amazon_search

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

With no annotations, the description carries full burden but only says 'search.' It fails to disclose that the tool requires authentication, has rate limits, or what the response contains. Essential behavioral context is missing.

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 single-sentence description is brief but under-specified. Conciseness is undermined by the lack of critical information; it is not efficiently front-loaded with key details.

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 complexity (7 parameters, including required credentials) and lack of output schema, the description is severely incomplete. An agent cannot reliably invoke this tool without additional information about parameters and authentication.

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%, and the description adds no meaning to the 7 parameters. It does not explain the purpose of searchIndex, itemCount, or credential fields, leaving the agent without guidance on parameter usage.

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 'Search for products on Amazon' clearly states the verb and resource, but it does not differentiate from sibling tools like amazon_browse or amazon_product, nor does it specify the search modality beyond keywords.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., amazon_browse, amazon_product). There is no mention of prerequisites such as API credentials (access_key, secret_key, partner_tag).

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