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

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds meaningful behavioral context: it returns machine-readable data, includes live guide counts, and covers classification conventions. It does not contradict annotations and supplements them with specifics about what data will be present.

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, information-dense sentence with no wasted words. It front-loads the main purpose ('Get the bicycle.guide vocabulary') and then efficiently lists the included components, making it easy to scan.

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 that the tool has no parameters, strong read-only annotations, and an output schema, the description fully covers the essential information. It names all major taxonomy categories and clarifies the machine-readable nature, so an agent has enough context to invoke it correctly without additional documentation.

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 and 100% schema coverage, so the baseline is 4. The description appropriately focuses on what the response contains rather than parameter details, which are nonexistent. No parameter documentation is needed here.

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 resource ('bicycle.guide vocabulary'), then enumerates the exact contents: domains, shelves with live guide counts, series, personas, guide_types, and classification conventions. This clearly distinguishes it from sibling tools like get_guide and list_guides, which target actual guides rather than vocabulary.

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 clearly indicates this tool is for retrieving machine-readable taxonomy data rather than prose, so the intended context is evident. It does not explicitly say when not to use it or name alternatives, but the 'rather than prose' phrasing and enumerated contents give enough context for an agent to select it over guide-fetching siblings.

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