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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds that results are machine-readable rather than prose and include 'live guide counts', signaling dynamic data. This adds useful behavioral context 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, information-dense sentence with a front-loaded verb/resource, followed by an enumerated list of contents and a clarifying format statement. Every element earns its place; there is no filler.

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 read-only, zero-parameter tool with an output schema present, the description fully specifies the resource and the kinds of data returned. The output schema covers return values, so the description does not need to explain them. Nothing an agent needs to call it correctly 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, so schema coverage is trivially 100%. No parameter-specific meaning is needed, and the baseline for zero-parameter tools is 4.

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?

States the specific verb 'Get' and resource 'bicycle.guide vocabulary', then enumerates exactly what is included: domains, shelves, series, personas, guide_types, and classification conventions. This clearly differentiates it from siblings like list_guides or get_guide, which concern guide content rather than the vocabulary itself.

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?

Provides clear context that this tool returns the taxonomy as machine-readable data rather than prose, implying it is the right choice when an agent needs vocabulary or classification conventions. It does not explicitly name alternatives or exclusion conditions, but the sibling list makes the intended use inferable.

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