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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful non-annotation context: that store results expose a domain key intended for retailmenot_store, which tells the agent how to consume the output. No contradiction.

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?

One tight sentence with the primary action and resource front-loaded, followed by the chaining hint. Nothing is wasted and no padding is present.

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 lookup tool with an output schema and safety annotations, the description supplies what structured fields don't: the downstream hand-off to retailmenot_store. It omits nothing critical, though it could note result ordering or that offers and stores are returned together.

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 parameter is documented as 'Store or brand search term'. The description restates this as 'free-text term' without adding format, matching behavior, or examples beyond the schema, so the 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?

States a specific verb (Find) plus the exact resources returned (RetailMeNot stores and cash-back offers) and the matching mode (free-text term). It also distinguishes itself from the sibling it feeds into by naming retailmenot_store, so an agent can place it in the workflow without opening other schemas.

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?

Clearly signals the use case and the downstream action: results carry the domain for retailmenot_store. It gives context and a chaining rule but does not state when NOT to use it (e.g., vs retailmenot_stores or retailmenot_cashback directly), leaving some alternative selection to inference.

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