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

Annotations already declare read-only, non-destructive, idempotent. The description adds valuable behavioral context: paginated results, 500+ active deals, and support for 12 Amazon marketplaces. This enriches what the agent knows beyond 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?

Extremely concise: two sentences, first one covers core functionality and fields, second adds pagination count and marketplace scope. No filler or redundant information. Front-loaded with the key action.

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?

Given an output schema exists, the description need not detail return values. It sufficiently covers tool purpose, data fields, pagination behavior, scale (500+ deals), and supported marketplaces. No obvious gaps for an agent to use it correctly.

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% with descriptions for both parameters (domain, page). The description adds no direct parameter detail but reinforces marketplace scope via '12 Amazon marketplaces', indirectly helping agents understand the domain parameter's purpose. Baseline 3 raised due to this extra context.

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?

Clearly states the verb 'browse' and resource 'Amazon current deals' with specifics: original vs deal price, product title, ASIN, deal link. Distinguishes from sibling tools like amazon.offers, amazon.product, amazon.search by focusing on 'deals' rather than general product info or search.

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 does not explicitly tell when to use this tool over siblings. It implies a broad use case (browsing deals) but lacks guidance on when not to use it (e.g., for specific product lookup or offer analysis). No alternatives or exclusions are mentioned.

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