Get dealer rating summaries (batch)

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

Beyond the readOnlyHint annotation, the description discloses useful behavioral traits: ~8s latency per uncached dealer, 30-minute caching, up to 5 dealers, and per-dealer failures not breaking the batch. This materially helps an agent predict performance and failure behavior.

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 compact sentences deliver function, limits, performance, caching, use case, and failure semantics without redundancy. Each clause earns its place and the core purpose is front-loaded.

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 single-parameter read-only batch tool with an output schema, the description covers the essential operational context: what it returns, batch size, latency, caching, and failure isolation. No critical information is missing.

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 input schema already documents the dealerIds parameter with min/max, pattern, source hint, and latency. Schema description coverage is 100%, so the main description adds no new parameter meaning beyond reinforcing the max of 5 dealers.

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 states a specific verb and resource: returns star histograms and average ratings for up to 5 dealers in one batch call. The batch nature and dealer count clearly distinguish it from the singular get_dealer_rating_summary sibling.

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 gives clear usage context: use this to vet all shortlisted sellers at once. It does not explicitly name alternatives or say when not to use it, but the batch framing and 'all shortlisted sellers at once' make the intended use obvious.

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