Retrieve App Store search suggestions from a partial keyword. Provide the term and optional country code to get suggested search terms for query completion.
Retrieve App Store search suggestions. Returns suggested search terms for the given partial keyword.
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Partial search term | |
| country | No | Two-letter storefront country code |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description only states it retrieves suggestions. It does not disclose behavioral traits such as rate limits, authentication requirements, or any side effects. For a read-only operation, minimal disclosure is expected but more context (e.g., return format limitations) would improve transparency.
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?
Two sentences, each serving a purpose: first states the action, second describes the output. No extraneous information, front-loaded with the verb. Efficient and clear.
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 and no annotations, the description is adequate but minimal. It does not specify the structure of suggestions (e.g., array of strings), potential errors, or limits (e.g., max 10 suggestions). For a simple suggest tool, this may suffice, but more completeness would be beneficial.
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% with descriptions for 'term' and 'country'. The description adds minimal nuance ('partial keyword' aligns with 'term'), but does not further clarify parameter constraints like valid country codes or maximum term length. Baseline score of 3 is appropriate given full schema coverage.
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's purpose: 'Retrieve App Store search suggestions' and specifies the output 'Returns suggested search terms'. It uses a specific verb ('Retrieve') and identifies the resource ('App Store search suggestions'), distinguishing it from sibling tools like appstore_search or amazon_suggest.
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 partial keyword autocomplete, but lacks explicit guidance on when to use this tool versus alternatives (e.g., appstore_search for full results, or google_suggest for web). No 'when not to use' or alternative recommendations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.