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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results include domains for retailmenot_store, which is useful cross-tool context, but doesn't discuss pagination, result size, or what a letter like 0-9 returns exactly.

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, front-loaded with the core action, followed by the routing constraint and the market hint. No filler.

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?

A read-only, two-param directory browser with an output schema, 100% schema coverage, and annotations covering safety. The description covers what it returns, when to use it, and the Canada variant, so nothing material 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 coverage is already 100%, and the schema documents the letter values and market values. The description adds semantic meaning beyond enum syntax: market=ca selects RetailMeNot Canada, which a bare enum value 'ca' does not convey on its own.

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 (List), resource (store), and scope (one letter of RetailMeNot's A-Z directory), and notes it includes domains for retailmenot_store. Clearly distinguishable from retailmenot_store and retailmenot_search siblings within the RetailMeNot family.

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 says to use it to browse when no search term is known, and names market=ca for Canada stores. It establishes the context, but does not name a specific alternative tool (e.g., retailmenot_autocomplete or search) to use instead when a term IS known.

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