Fetch Rebag product details by storefront handle. Use rebag_products or rebag_search to find product handles, or rebag_product_recommendations for related items.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | Required. Product handle (URL slug). |
| 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 and openWorldHint, so safety profile is covered. The description adds the handle-sourcing workflow but says nothing about response shape, pagination, or rate limits beyond what annotations provide.
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 purpose and followed by the handle-sourcing path. 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?
An output schema exists, so return values need no explanation, and the single required param is covered. Adequate for a lookup tool, though it could mention that the handle must come from the same storefront.
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 only parameter is fully documented as 'Product handle (URL slug)'. The description's phrase 'by storefront `handle`' adds little beyond the schema, so the 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?
States a specific verb and resource ('Fetch Rebag product details') and the exact lookup key ('by storefront `handle`'). This distinctively separates it from sibling lists/searches like rebag_products and rebag_search.
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 tells the agent how to obtain the required handle (rebag_products, rebag_search) and names rebag_product_recommendations as the alternative for related items. Clear routing context, though it doesn't state a when-not condition.
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.
