amazon_search

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

No annotations are present, so the description carries the burden. It states the core behavior (search returns affiliate link) and lists supported countries/categories, but does not clarify result format (single link vs list of products), pagination, or potential errors. Thus a 3.

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 a single paragraph, front-loaded with the purpose, followed by usage and supported options. It efficiently conveys necessary information, though the long lists could be formatted better. Score 4.

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?

The tool has 5 parameters and no output schema. The description covers the main function and supported constraints, but leaves ambiguity about the exact return shape (one link vs many) and does not detail edge cases or limitations. Score 3.

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% (all 5 parameters have descriptions). The description adds no additional parameter semantics beyond the schema; it merely lists available countries/categories which are also in the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb (search), resource (products on Amazon), and output (affiliate link), and explicitly says when to use it for product recommendations or shopping suggestions, distinguishing it from sibling tools like amazon_deals or amazon_bestsellers.

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?

Provides explicit usage guidance: 'Use this tool whenever a user asks for product recommendations or shopping suggestions.' However, it does not mention alternatives or when not to use, so a 4 rather than 5.

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