Generate Shop.app autocomplete suggestions from a search query, with an optional limit up to 20 (default 10).
Suggest Shop.app searches. Returns Shop.app autocomplete suggestions. Limit defaults to 10 and supports up to 20.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum suggestions, defaults to 10 and supports up to 20 | |
| query | Yes | Search query |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It only mentions the limit default and maximum, but lacks details on rate limits, caching behavior, or input validation. This is minimal for a suggestion tool.
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 two concise sentences, front-loading the purpose and adding a behavioral note about the limit. No unnecessary words.
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 no output schema, the description does not explain the return format (likely a list of strings). For a simple autocomplete tool, this may be acceptable, but the description could be more complete by hinting at output structure.
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 100%, so the schema already documents parameters. The description adds the default limit value (10) and max (20), which is a minor addition over the schema. Baseline 3 is appropriate.
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 suggests Shop.app searches and returns autocomplete suggestions. This distinguishes it from sibling tools like shop_app_search (which likely returns full search results) and shop_app_shop_typeahead (which is shop-specific).
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 implicitly suggests use for autocomplete functionality, but does not explicitly state when to use this tool versus alternatives like shop_app_search or shop_app_suggestions. There is no 'when not to use' guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.