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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description doesn't need to restate safety. It adds useful behavioral context beyond the annotations: the data includes live guide counts and is returned as machine-readable data rather than prose. No contradictions with 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 sentence that leads with the action and resource, then provides a compact list of contents. Every element adds information, and there is no fluff. The description is long enough to be specific but not bloated.

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?

With zero parameters and an output schema present, the description covers everything an agent needs to decide to call it. It specifies the scope of the returned vocabulary and the live-count detail. No gaps are apparent for a read-only list tool.

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 accepts zero parameters, so the description has no parameter documentation burden. The schema coverage is trivially 100%. The description's content listing gives context about what the returned data will contain, which is the relevant semantic information 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 names a specific verb ('Get') and a specific resource ('the bicycle.guide vocabulary'), then enumerates the included components (domains, shelves, series, personas, guide_types, classification conventions). This makes it immediately distinguishable from sibling tools like get_guide, list_capabilities, and list_guides, which operate on different resources.

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 clearly implies when to use this tool: when you need the taxonomy/vocabulary as machine-readable data. The phrase 'rather than prose' hints at a use-case distinction, but it does not explicitly name alternatives or state when not to use the tool. Still, the context is clear enough for a zero-parameter retrieval tool.

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