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

Annotations already establish the tool as read-only and non-destructive. The description adds useful behavioral context: the tool returns machine-readable structured data and includes live guide counts, which signals both format and dynamic content beyond the basic read-only annotation.

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 no filler. Every clause adds specific information about the returned taxonomy, and the core purpose is front-loaded with 'Get the bicycle.guide vocabulary'.

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 parameterless, read-only tool with an output schema, the description provides sufficient context. It names all major components of the taxonomy and clarifies the data format, so an agent has everything needed to decide when to call it.

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 are no parameter semantics to document. The description compensates by enumerating what the returned vocabulary contains, making the tool's output scope clear despite having no input schema details.

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 clearly specifies the operation ('Get') and the resource ('bicycle.guide vocabulary'), then enumerates the exact kinds of data included: domains, shelves, series, personas, guide_types, and classification conventions. This makes it easy to distinguish from siblings 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 phrase 'as machine-readable data rather than prose' gives clear context that this tool is for structured vocabulary retrieval. It does not explicitly name alternatives or state when not to use it, but the scope is clear enough for an agent to select it appropriately.

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