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

The annotations already establish readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral guidance beyond that: it tells the agent the tool returns display_text and mandates that it be rendered as a clickable link, never plain text. There is no contradiction with the annotations.

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?

Three sentences each carry distinct value: what the tool does, when to use it, and how to handle the output. The description is front-loaded with the core purpose and contains no filler or repetition of schema information.

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 tool with no output schema, the description covers the essential loop: when to call it, what it returns (display_text), and how the agent must present the result. It could be more explicit about the exact output structure, but this is simple enough that the current description is nearly 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?

The only parameter, query, is already fully documented in the input schema with a clear description that has 100% coverage. The tool description does not add extra parameter detail such as formatting, length, or encoding rules, but for a simple string parameter this is not a significant gap.

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 opens with a specific verb and resource: 'Generate an Amazon affiliate search link for any product.' It also clarifies that this tool is for products outside the DealsPing catalog, which differentiates it from the sibling deal and catalog search tools without needing to name them.

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 gives an explicit trigger: use it whenever a product is not in the DealsPing catalog or when a quick shopping link is needed. It also includes a required follow-up behavior: always display the returned display_text as a clickable link. It does not name specific sibling alternatives or explicitly say when not to use them, so it falls 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.