amazon_autocomplete

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

No annotations are provided, so the description carries the full burden. It discloses credit cost and clarifies parameter behavior (prefix effectively required), but does not mention read-only nature or rate limits. Overall, it provides useful behavioral context beyond basic purpose.

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 and front-loaded with purpose. It includes necessary details about credits and return format without unnecessary verbosity. A slight amount of extra text could be trimmed, but overall efficient.

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 that there is no output schema, the description explains the return format (flat array of suggestion objects). All parameters are covered both in schema and description, and the effective requirement for prefix is noted. Fairly complete for a tool of this complexity.

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%, so baseline is 3. The description adds value by explaining that prefix is effectively required, describing the return format, and providing context for parameters like last_prefix and suffix. This goes beyond what the schema provides.

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 it retrieves keyword suggestions from Amazon's autocomplete feature based on partial search terms. It uses specific verbs and resources, and is distinct from sibling tools like amazon_search and google_autocomplete.

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 mentions it's useful for keyword research and search-driven features, and notes that prefix is effectively required. It implies when to use but does not explicitly state when not to use or name alternatives, though context from sibling tools makes it clear.

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