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

Annotations already declare readOnlyHint and non-destructive behavior. The description adds useful behavioral context beyond that by promising live guide counts and machine-readable output rather than prose. There is no contradiction with annotations, and no hidden state-changing behavior is implied.

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 with no filler. The enumeration of returned vocabulary elements earns its place, and the clarification 'machine-readable data rather than prose' adds value without bloating the description.

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 vocabulary tool with an output schema, the description is complete: it names the resource, the returned categories, and the data format. An agent has enough information to decide to call it and know what to expect.

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 is no parameter burden for the description to carry; the empty schema is already unambiguous and schema description coverage is 100%. The nominal baseline for zero-parameter tools applies.

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 and resource: 'Get the bicycle.guide vocabulary' and enumerates the exact returned components (domains, shelves, series, personas, guide_types, classification conventions). It does not explicitly call out a sibling alternative, but the resource name and content list make the tool's purpose clear.

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 intended use is implied rather than explicit: an agent can infer to call this when it needs taxonomy or classification data instead of a specific guide, guide list, or capability list. However, there is no direct 'use when' guidance or comparison with siblings like get_guide, list_guides, or list_capabilities.

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