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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context beyond the annotations by noting shelf counts are 'live' and that the output is 'machine-readable data rather than prose', which informs the agent about dynamic values and response format.

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, front-loaded sentence that begins with the core purpose and then lists the taxonomy components in a compact, scannable way. Every element named is meaningful and no filler or redundant phrasing is present.

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 parameterless, read-only tool with an output schema already defined, the description is complete. It names the full set of taxonomy categories, notes live counts, and signals the machine-readable nature of the response, so an agent has enough context to invoke it correctly without additional guidance.

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, so the schema provides no parameter semantics to clarify. The description compensates by explaining exactly what data the response includes, making parameter-related ambiguity low.

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 identifies the exact resource ('bicycle.guide vocabulary'), then enumerates the contents: domains, shelves with live guide counts, series, personas, guide_types, and classification conventions. This makes it clearly distinct from siblings like list_guides (which would return guides) and get_guide (which would return a single guide). The phrase 'as machine-readable data rather than prose' reinforces what kind of response this tool provides.

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 the tool is for retrieving the taxonomy/vocabulary rather than actual guide content, but it does not explicitly state when to choose it over list_guides, get_guide, or list_capabilities. No exclusions or alternative-conditions are given, so an agent must infer usage from the resource name and contents.

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