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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds value by specifying the exact data categories returned and noting that shelf counts are 'live,' which indicates dynamic behavior. This exceeds what the annotations alone convey.

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 with the main purpose front-loaded. Every element adds useful information: the resource, the specific vocabulary components, live counts, and the machine-readable output distinction. 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?

With no parameters, safety annotations, and an output schema present, the description covers what an agent needs: the tool's scope, contents, and output format. The enumerated categories make the expected result clear without needing to explain return values.

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 there is nothing for the description to document. Baseline for zero parameters is 4, and the description appropriately focuses on output rather than input semantics.

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') and enumerates exactly what is included: domains, shelves with live guide counts, series, personas, guide_types, and classification conventions. This clearly differentiates it from sibling tools like list_guides or get_guide.

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 it—when structured vocabulary/taxonomy data is needed rather than prose—but it does not explicitly state when to avoid it or name alternative tools. The 'rather than prose' phrase gives some context, but the guidance is mostly implicit.

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