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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no safety contradiction exists. The description adds useful behavioral context beyond annotations by clarifying that the output is machine-readable data, includes live guide counts for shelves, and covers classification conventions rather than just a flat list.

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, front-loaded sentence that begins with the tool's core purpose and then packs the payload list without fluff. Every listed item adds meaning about the taxonomy scope, and the 'rather than prose' contrast earns its place by setting response expectations.

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?

Given zero parameters, rich annotations, and an output schema, the description covers what an agent needs to decide whether to call this tool. It names the main taxonomy areas and clarifies the machine-readable nature, while the output schema can handle detailed return-value documentation.

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 the baseline is 4. The description appropriately focuses on what the tool returns rather than parameter behavior, since there is nothing to document at the parameter level.

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 ('Get') and clearly identifies the resource as the bicycle.guide vocabulary, enumerating its concrete components: domains, shelves, series, personas, guide_types, and classification conventions. This differentiates it from sibling tools like list_guides or get_guide, which are about guides themselves rather than the taxonomy.

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: call this when you need the program's vocabulary as machine-readable data rather than prose. It does not explicitly state when to use this tool versus list_capabilities or list_guides, nor does it mention exclusions. The distinction from siblings is left mostly to inference from the tool name and contents.

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