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

Annotations already establish this as a safe read-only operation. The description adds value beyond those annotations by specifying what will be returned, including live guide counts and classification conventions, and by clarifying that the output is machine-readable data rather than prose.

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 that front-loads the core purpose and then enumerates the included content. Every phrase adds value, with no filler or redundant restatement of the tool name.

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 zero parameters, strong read-only annotations, and an output schema present, the description needs only to communicate scope and format. It does so thoroughly by listing the taxonomy components and the machine-readable output expectation, making it complete for an agent to call 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 accepts zero parameters and the schema coverage is 100%, so there are no parameter semantics to explain. The description still adds meaningful information about what the returned taxonomy contains, satisfying the baseline for a no-parameter tool.

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 a clear resource, the bicycle.guide vocabulary, while enumerating the exact contents: domains, shelves, series, personas, guide_types, and classification conventions. This clearly distinguishes it from sibling tools like list_guides and get_guide, which concern guides rather than taxonomy.

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 usage when structured vocabulary or classification data is needed, especially with the phrase 'as machine-readable data rather than prose.' However, it does not explicitly state when to prefer this over list_guides or list_capabilities, nor does it mention any exclusions.

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