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

Annotations already declare readOnlyHint and idempotentHint. Description adds behavioral context beyond annotations: 'Use this once' suggests a one-time lookup pattern, and the workflow hint about shop_vehicles clarifies how to chain calls. No contradictions.

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?

Three succinct sentences, each delivering essential information (purpose, workflow hint, sibling differentiation). No redundant or filler content.

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 the output schema exists and sibling tools are listed, the description covers purpose, return value outline (IDs, addresses, listing counts), usage pattern, and guidance for alternative tools. Sufficient for agent decision-making.

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?

Schema description coverage is 50% (country, location documented). Description clarifies query is for name/place but does not detail limit parameter. While it adds some context, it doesn't fully compensate for the undocumented parameters; baseline 3 is appropriate.

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?

States 'find dealerships by name/place' with clear output (IDs, addresses, listing counts). Explicitly distinguishes from get_dealership (contacts/hours) and shop_vehicles (stock via dealer_id), which are sibling tools.

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?

Directs agent to use this tool once to obtain a dealer ID, then call shop_vehicles for stock; also tells when to use get_dealership instead (contacts/hours). Provides clear when-to-use and when-to-avoid guidance relative to siblings.

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