Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context: it returns machine-readable data rather than prose, and mentions 'live guide counts', implying dynamic counts rather than static values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence that front-loads 'Get the bicycle.guide vocabulary' before listing specific contents. Every element earns its place; no filler or redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only vocabulary listing, the description covers what is returned (domains, shelves, series, personas, guide_types, conventions) and the output format (machine-readable data). An output schema exists, so structural details can be inferred from there.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the schema fully covers parameter needs. The description doesn't need to explain parameter semantics; the 'machine-readable data rather than prose' phrasing gives a hint about the return format, which is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and a precise resource ('bicycle.guide vocabulary'), enumerating concrete components like domains, shelves, series, personas, and guide_types. It clearly distinguishes itself from sibling tools by focusing on vocabulary rather than individual guides or capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use case: when an agent needs taxonomy/classification data rather than guide content or capabilities. It doesn't explicitly state when not to use it or name alternatives, but the resource specificity makes the context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.