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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context by promising 'machine-readable data rather than prose' and noting that shelf counts are live, which informs expectations about the response without contradicting the annotations.

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?

A single, front-loaded sentence efficiently states the purpose, enumerates the taxonomy contents, and conveys the structured-data nature of the response. Every phrase earns its place; no filler or redundant restatement exists.

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, an output schema present, and annotations covering safety, the description provides the remaining context needed to invoke the tool correctly: exactly which vocabulary segments are returned and in what form. Nothing essential is missing.

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 full schema coverage, so there is no parameter documentation burden. Per the baseline for zero-parameter tools, this receives a 4; the description also adds semantic value by clarifying exactly what data categories the empty-parameter call returns.

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 names a concrete resource ('the bicycle.guide vocabulary'), then enumerates its contents: domains, shelves, series, personas, guide_types, and classification conventions. This clearly distinguishes it 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 conveys clear context for when to use the tool: when the agent needs the structured vocabulary rather than individual guides or lists of guides. It does not explicitly state when-not-to-use or name alternatives, but the resource enumeration makes the appropriate use case obvious.

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