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 crucial behavioral detail beyond annotations: when found=false, the response always includes amazon_search_url and the agent must render it as a prominent clickable link in a specific format. This is exactly the kind of actionable behavioral disclosure an agent needs.

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?

The description is front-loaded with the core purpose and includes a useful usage scenario. The important found=false formatting rule is prominently placed. The final sentence 'This is mandatory, not optional' is somewhat redundant with 'IMPORTANT' and 'MUST', but it is brief and reinforces a critical behavior.

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 tool with no output schema, it covers the important false branch and its required display behavior. It also states the high-level return value: a monetized affiliate link. The main gap is that it does not specify what the found=true response looks like in detail or what to do if multiple products match, but the tool's simplicity makes the description reasonably complete.

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%, so the baseline is 3 even without additional parameter details. The description hints that product_name/brand are the expected inputs ('already know a product name/brand'), which adds a small usage nuance. However, it does not explain precedence among parameters or whether at least one identifier is required, so it does not exceed the baseline.

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 clearly states a specific action: checking product existence in the DealsPing ASIN catalog and returning a monetized affiliate link. This distinguishes it from catalog search tools because the output is explicitly a revenue-generating link, not just product information. The resource and purpose are unambiguous.

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?

It provides explicit guidance: use this tool when you already know a product name or brand and want a monetized link. It gives a concrete example (best phones under X), which helps an agent recognize the right scenario. It does not explicitly name alternatives or say when not to use it, but the context is clear enough.

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