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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the core safety profile is clear. The description adds meaningful behavioral context beyond annotations by noting that shelf guides counts are 'live' and that the output is structured machine-readable data rather than prose.

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 resource name and then efficiently lists the exact contents. Every element earns its place; there is no filler or repetition.

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 parameterless read-only tool with an output schema and strong annotations, the description is complete: it names the domain, the categories included, the live nature of counts, and the machine-readable format. Nothing essential is missing for an agent to understand what it will receive.

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 not a burden on the description. The description appropriately focuses on what the returned vocabulary contains rather than parameter details.

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'), a clear resource (the bicycle.guide vocabulary), and enumerates exactly what is included: domains, shelves, series, personas, guide_types, and classification conventions. It clearly distinguishes the tool's machine-readable output from prose-based tools like get_guide.

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 phrase 'as machine-readable data rather than prose' implies a use case and hints at distinguishing this from a prose-oriented sibling, but it never explicitly names alternatives or states when to choose this tool over list_guides or list_capabilities. Usage context is present but only implicitly.

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