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 useful behavioral nuance by noting 'live guide counts' and 'machine-readable data rather than prose,' setting expectations about freshness and 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 focused sentence with the main point front-loaded: 'Get the bicycle.guide vocabulary.' Every clause adds specific value, from listing taxonomy components to noting live counts and machine-readable format, with no filler.

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?

With no required parameters, an output schema present, and read-only annotations, the description is complete for safe invocation. It identifies all relevant taxonomy categories and behavioral expectations, so an agent has enough information to call the tool correctly.

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 an empty input schema, so there are no parameter semantics to explain. The description's enumeration of returned categories adds meaningful context about what the parameterless call returns, which satisfies the baseline for this case.

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 and resource ('Get the bicycle.guide vocabulary') and explicitly enumerates the contents: domains, shelves with live guide counts, series, personas, guide_types, and classification conventions. This clearly differentiates it from siblings like list_guides and get_guide, which concern guides rather than the taxonomy 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 gives clear context for when to use the tool: whenever an agent needs the guide program's vocabulary or taxonomy, including shelves and guide types. It does not name sibling tools or provide explicit exclusions, but the scope is unambiguous enough that selection should be straightforward.

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