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 non-derivable behavioral context: that store results include a domain field intended to be forwarded to retailmenot_store, which tells the agent how to chain calls.

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 front-loaded sentence stating the operation first and the downstream chaining detail second. No filler, though the semicolon-joined clause could be slightly tightened.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description covers purpose, the scoping input, and the follow-on call, leaving only minor gaps around when this beats sibling listing tools.

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?

There is one parameter with 0% schema description coverage, so the schema itself documents nothing. The description compensates partially by characterizing 'term' as 'free-text', but gives no format, matching rules, or examples, so it only marginally exceeds the bare schema.

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') and resources ('RetailMeNot stores and cash-back offers') scoped by a free-text term, and positions the tool against the sibling retailmenot_store by noting it feeds the domain forward. An agent can tell it is the discovery/autocomplete step rather than the detail fetch.

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 clause 'store results carry the domain to pass to retailmenot_store' implies the intended workflow (autocomplete first, then detail lookup), which is useful. However, it never states when to choose this autocomplete entry point over siblings like retailmenot_stores or retailmenot_cashback, so the guidance is implied rather than explicit.

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