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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds content structure (price, valid service methods, tiered groups), which is helpful context, but it discloses nothing about auth, rate limits, or freshness — and much of what it describes overlaps with the output schema. A 3 is appropriate.

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?

A single sentence with the resource front-loaded and the two content categories efficiently enumerated after the colon. No padding or redundancy, though the phrasing is dense enough to border on jargony.

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 one-parameter read-only lookup with a full output schema and documented parameter, the description is sufficient: it tells the agent what resource it targets and what kind of items come back. Nothing critical 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?

Schema description coverage is 100% and the single store_id parameter is fully documented in the schema (including its source, /dominos/store-locator). The description only implies store scoping and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 resource (a single Domino's store's coupons and deals) and even enumerates the two content shapes returned (standalone coupons vs. tiered volume-discount groups). It clearly differentiates from menu/nutrition siblings by being coupon-scoped, though it does not name an alternative tool explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as dominos_store or dominos_menu. The agent must infer that this is the coupon-retrieval tool purely from the name and resource phrase.

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