Fetch customer questions and answers for a Best Buy product by its numeric SKU. Use bestbuy_product to confirm the item or bestbuy_product_reviews for ratings and review text.
| Name | Required | Description | Default |
|---|---|---|---|
| sku | Yes | Required. Numeric Best Buy SKU, e.g. from a bestbuy_product result's sku field. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds only the numeric-SKU constraint and confirms Q&A content, with no extra behavioral detail (e.g., pagination, whether answers may be empty); with annotations carrying the safety profile a 3 is appropriate.
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 tight sentences, front-loaded with the action, followed by the disambiguation. No wasted 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?
A single-parameter read tool with an output schema and read-only annotation needs little more than the purpose, the SKU source, and sibling routing, all of which are present. Nothing required for correct invocation is missing.
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 sku property already documents 'Required. Numeric Best Buy SKU.' The description's 'numeric SKU' phrasing only restates the schema, so the baseline 3 holds.
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?
States a specific verb (Fetch) plus resource (customer questions and answers), scoped to a Best Buy product identified by numeric SKU. It also names the siblings bestbuy_product and bestbuy_product_reviews, so an agent can distinguish it without opening any schema.
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?
Explicitly routes the agent to alternatives: use bestbuy_product to confirm the item, bestbuy_product_reviews for ratings/review text. Clear context for choosing between the three, though it never states an explicit when-not condition for this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
