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

Annotations already indicate read-only, non-destructive behavior, so the description need not repeat that. It adds some useful context by noting 'live guide counts' and that the result is 'machine-readable data rather than prose,' but it does not disclose other behavioral traits like ordering, completeness, or response specifics.

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 lists concrete deliverables. It is longer than ideal due to the many category names, but every listed item adds useful information and there is no wasted prose.

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, in what form, and includes enough detail to distinguish it from siblings. Nothing essential is missing for an agent to invoke it 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 parameter semantics are largely not applicable; the schema covers everything. The description adds value by enumerating the taxonomy categories and conventions the caller will receive, exceeding 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 opens with a specific verb and resource: 'Get the bicycle.guide vocabulary.' It then enumerates exactly what is included (domains, shelves, series, personas, guide_types, and classification conventions), which clearly distinguishes it from sibling tools like list_guides or list_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?

The description implies usage: an agent should call this when it needs the structured taxonomy or classification conventions rather than guides or capabilities. However, it does not explicitly state when to use this tool versus its siblings or mention any exclusion conditions.

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