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

Annotations already indicate this is a safe read-only operation. The description adds useful behavioral context beyond annotations: it returns 'machine-readable data rather than prose' and notes that shelf counts are 'live', which suggests dynamic data rather than a static snapshot.

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 and then efficiently enumerates the taxonomy contents. Every clause adds information about what the caller can expect, 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?

For a zero-parameter, read-only tool with an output schema, the description is fully adequate. It tells the agent what data categories are included, highlights live counts, and clarifies the machine-readable output format, leaving no critical gap for invocation.

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 parameter documentation is not a burden on the description. With 100% schema coverage and an empty parameter list, the description appropriately focuses on what the response contains 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 opens with a precise verb and resource: 'Get the bicycle.guide vocabulary'. It enumerates the specific content areas returned (domains, shelves, series, personas, guide_types, classification conventions), making the tool's scope unmistakable and clearly distinct from siblings like get_guide and list_guides.

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 makes it clear that this tool is for retrieving vocabulary/taxonomy data rather than actual guides or capabilities, so the appropriate usage context is implied. However, it does not explicitly state when to choose this tool over list_guides or list_capabilities, nor does it name alternatives.

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