Get dealer rating summary

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

The description reveals significant behavior beyond the readOnlyHint and openWorldHint annotations: it makes 5 lightweight requests, takes ~8s uncached, and is cached for 30 minutes. It also explains that the summary is reconstructed from per-star counts, which is useful operational context for the agent.

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?

Two tight sentences deliver the output definition, operational cost, caching, the usage scenario, and the sibling alternative. Information is front-loaded and every clause earns its place with no repetition of schema or annotation 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?

With one fully documented required parameter, an output schema present, explicit cost/latency/caching behavior, and a named alternative, nothing critical is missing. An agent can confidently decide when to call this tool and roughly what to expect in return.

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 100%, and the schema already provides a precise, disambiguating description for dealerId: 'from get_watch's sellerIds (NOT the customerId). The tool description does not add extra param info, but none is needed because the schema does the heavy lifting.

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?

Description states the resource (dealer rating summary), the specific output (star histogram and weighted average rating), and how it is produced (reconstructed from per-star review counts). This clearly distinguishes it from the plural sibling, get_dealer_rating_summaries, and from get_dealer_ratings, which would contain individual ratings.

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?

Explicitly tells the agent when to use this tool: 'use it to vet an unfamiliar dealer before recommending a purchase.' It also gives the alternative condition: 'For several dealers, prefer get_dealer_rating_summaries.' This is direct routing guidance with no ambiguity.

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