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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds some useful context, such as 'live guide counts' and 'machine-readable data rather than prose,' but does not disclose deeper behavior beyond what annotations and the output schema already imply.

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 focused sentence that front-loads the core purpose ('Get the bicycle.guide vocabulary') and then packs in specific, useful detail. There is no fluff 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?

Given zero parameters, read-only annotations, and a provided output schema, the description is complete enough for an agent to select and invoke the tool correctly. It clearly states what the vocabulary contains and notes that the data is machine-readable.

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 and an empty input schema, so there are no parameter meanings to explain. The description adds value by specifying the content of the returned vocabulary, which is more than necessary 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 uses a specific verb ('Get') and clearly identifies the resource: the bicycle.guide vocabulary. It enumerates the exact categories returned (domains, shelves, series, personas, guide_types, classification conventions), which distinguishes it from siblings like get_guide and list_guides.

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 usage context is implied: an agent would use this tool when it needs the taxonomy or classification conventions of the guide program. However, it does not explicitly mention when not to use it or name alternatives such as 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.