amazon_search

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions output includes organic/sponsored positions, prices, ratings, and image URLs, but does not address pagination behavior, result count per page, rate limits, or authentication needs. Adequate but not fully transparent.

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 sentence with a clear verb and a returns clause. No wasted words; front-loaded with purpose.

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 search tool with multiple parameters (sorting, pagination, domain) and no output schema, the description lacks details on result structure, items per page, and sorting behavior. It does not connect to sibling tools or mention prerequisites.

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 only 20% (only query has a description). The description does not explain parameters like domain, sort_by, start_page, or pages, leaving their semantics unclear. It adds minimal value beyond the schema defaults and enums.

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 the tool runs an Amazon keyword search and lists the returned data: ranked product listings with organic/sponsored positions, prices, ratings, and image URLs. It distinguishes from siblings like amazon_product (single product) and batch tools.

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 usage for searching Amazon, but does not explicitly state when to use this tool versus siblings like amazon_product for detail retrieval or batch tools for bulk operations. No guidance on when not to use it.

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