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

The annotations already establish that this is a read-only, non-destructive operation. The description adds value beyond the annotations by specifying what data is returned, including dynamic 'live guide counts,' and by clarifying that 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?

One well-structured sentence front-loads the main purpose and then enumerates the exact vocabulary components. Every element earns its place, and the list of contents is valuable for agent decision-making without being verbose.

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 complete. It states what the tool returns and the structured nature of the result, so an agent has enough information to select and invoke the tool 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 has zero parameters, so the schema leaves no ambiguity. The baseline for zero-parameter tools is 4; the description adds no parameter information because none is needed.

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 precise resource: the bicycle.guide vocabulary. It enumerates the contents (domains, shelves, series, personas, guide_types, conventions), which clearly distinguishes it from the sibling tools that retrieve guides or capabilities.

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?

Though the purpose is clear, the description does not explicitly explain when to choose this tool over list_guides, list_capabilities, or get_guide. Usage is implied: an agent needing the vocabulary or classification conventions should use this, but no exclusions or alternative conditions are stated.

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