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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds behavioral context by specifying that the data includes live guide counts and is returned as machine-readable data rather than prose, which is genuinely useful beyond the structured annotations.

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?

The description is a single dense sentence that front-loads the core purpose ('Get the bicycle.guide vocabulary') and then lists the included categories with a clarifying format note. Every phrase adds information, and there is no filler or repetition.

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?

Given zero parameters, a rich output schema, and annotations covering read-only behavior, the description fully equips an agent to decide whether and how to invoke this tool. It enumerates the vocabulary categories and explicitly frames the output format, so nothing essential is missing.

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?

The tool has zero parameters and schema description coverage is 100%, so the schema is effectively complete. The description appropriately explains what the returned vocabulary contains, which is the relevant semantic contribution for a parameterless call.

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 specific resource ('bicycle.guide vocabulary'), then enumerates the exact contents: domains, shelves, series, personas, guide_types, and classification conventions. This clearly distinguishes it from sibling tools that retrieve guides or capabilities rather than the vocabulary itself.

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 when to use this tool: when an agent needs the guide program's vocabulary or classification conventions as structured data. It does not explicitly name alternatives or provide exclusion criteria, but the contrast with 'rather than prose' plus the listed contents makes the intended context clear.

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