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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond annotations by disclosing the data-source limitation — 'catalog is a lightweight product index, not a live price feed' — and that results contain affiliate links, which are notable output traits.

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 sentences with zero filler: the action and return value are front-loaded in the first sentence, and the critical caveat is delivered in a single parenthetical clause in the second. Every sentence earns its place.

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 low-complexity read-only search with four optional, fully documented parameters, the description covers both the return value and the key limitation. The only real ambiguity is behavior when no filters are supplied (an empty search returning everything is implied but not stated), and there is no output schema to lean on, so a full 5 is not warranted.

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 100%, so every parameter (query, category, brand, limit) already has its own description, including the limit range and query match target. The description only reinforces the search dimensions ('by keyword, category, or brand') without adding combination, precedence, or format details, 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?

The description names a specific verb ('Search') and resource ('DealsPing ASIN catalog'), and states exactly what is returned ('products with ready-to-use affiliate links'). The 'catalog... not a live price feed' contrast implicitly distinguishes it from the sibling search_deals, so an agent can tell them apart even without opening the schema.

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 a clear when-not-to-use signal: 'no price/availability data' and 'not a live price feed' tells an agent seeking live pricing that this is the wrong tool. However, it does not explicitly name the alternative (e.g., search_deals or get_deals_by_price), which keeps it just short of a 5.

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