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

Annotations already disclose read-only and non-destructive behavior. The description adds useful behavioral context by noting the result is 'machine-readable data rather than prose' and that shelf counts are 'live', which helps an agent understand the output's nature 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?

The description is a single dense sentence that front-loads the action and resource, then lists the taxonomy components and output format. Every clause earns its place; there is no filler or repetition beyond the needed scope clarification.

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 no-parameter, read-only listing tool with an output schema present, the description is sufficiently complete. It names the exact vocabulary components returned, signals the machine-readable format, and the empty input schema means there is no call-construction ambiguity.

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 description carries no parameter-documentation burden. The empty schema already fully covers the input side, and the baseline of 4 is appropriate because there is nothing for the description to add.

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 clearly identifies the action ('Get') and resource ('the bicycle.guide vocabulary') and enumerates specific contents such as domains, shelves, series, personas, and guide_types. It is far more informative than the title, but it does not explicitly differentiate itself from the sibling tools like list_guides or list_capabilities.

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 a clear use case: retrieve the guide program's structured vocabulary rather than prose. However, it does not explicitly state when to prefer this tool over the sibling tools or when not to use it. The usage guidance is inferable but not stated.

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