search_amazon

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

With no annotations, the description carries the burden. It mentions scraping via 'max_pages to scrape,' hinting at web scraping behavior, and lists returned fields. However, it does not disclose other traits like rate limits, authentication needs, or potential volatility.

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 concise (5 lines) with a clear front-loaded purpose statement, followed by parameter details. Every sentence serves a purpose with no redundancy.

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 the simple tool (2 parameters, with output schema), the description covers the purpose, return fields, and parameter explanations. It lacks errors or limitations but is complete enough for an agent to use effectively.

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 0%, so the description compensates by explaining parameters: query is a 'Product search query, e.g. wireless headphones' and max_pages is 'Number of result pages to scrape (default 1).' This adds meaningful context beyond the schema.

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 'Search Amazon products and return title, price, rating, and image,' specifying the verb (search) and resource (Amazon products), which distinguishes it from sibling tools like search_github or search_books.

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 implies use for Amazon product searches but does not explicitly state when to use versus alternatives. No exclusions or when-not-to-use guidance is provided, making it adequate but not explicit.

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