Generate Amazon typeahead keyword suggestions from a prefix. Use the public suggestion API for amazon.com to discover search terms for product and SEO research.
Retrieve Amazon search suggestions. Returns typeahead keyword suggestions from Amazon's public suggestion API for amazon.com.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | Suggestion prefix |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It states it returns suggestions from a public API, but does not disclose rate limits, caching, or the exact return format. It provides basic transparency but lacks detail.
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 only two sentences, front-loaded with the primary action, and contains no superfluous information. Every word serves a 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 simple tool with one required parameter and no output schema, the description is mostly complete. It specifies the source and scope. However, it could mention the return format (e.g., array of strings) for full completeness.
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% and the parameter description 'Suggestion prefix' already clarifies semantics. The tool description adds no new parameter-level information, matching the baseline score.
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 verb 'Retrieve' and the resource 'Amazon search suggestions', specifying it returns typeahead keyword suggestions. It distinguishes from sibling suggest tools by naming 'amazon.com' and the typeahead nature.
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 like `amazon_search` or other suggest tools. The description only explains what the tool does, without context on when it is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.