Guide

Keep the summary useful without making it heavy.

A description should explain the page quickly. Too little can feel vague, and too much can bury the point.

OpenToolsKit's description checker helps you tighten the draft before you publish.

Trust and sourcing

Reviewed, updated, and sourced.

OpenToolsKit keeps the public trust layer visible: how the page is maintained, when it was last reviewed, and which sources matter when the workflow touches rules or specs.

A description is a summary, not a paragraph

Good metadata gives a reader the shape of the page fast.

It should not try to explain everything at once.

Start with the value, not the filler

Many descriptions waste the first words on generic language.

That makes the useful part arrive too late.

Review it next to the title

A description makes more sense when it is checked alongside the title and URL.

That is why snippet previews matter too.

Workflow support

Keep the surrounding workflow attached to the guide.

Collections compare the best route for the job, while packs connect the wider multi-step workflow that usually follows.

FAQ

Short answers that keep the workflow moving.

Should the description repeat the title?

Not exactly. It should support the title, not clone it.

Will search always use my description?

No. Search engines can still rewrite or choose other text.