Fetch normalized product details for one Allbirds item using its URL slug handle. The storefront is set server-side for consistent product data.
Get a Allbirds product. Returns normalized product detail for one Allbirds (https://www.allbirds.com) product handle. The storefront URL is fixed server-side; handle is the product's URL slug.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | Product handle |
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully explains that the storefront URL is fixed server-side and that the handle is the URL slug, and it states the return is normalized product detail. However, it does not mention whether the operation is read-only, what happens for invalid handles, or any error/response behavior.
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-loads the core action and output, and adds the parameter clarification without any wasted words. Every sentence contributes useful information.
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 low-complexity, single-parameter tool, the description is largely complete: it identifies the resource, the input semantics, and the return type. It does not describe error cases or explicitly confirm read-only behavior, but given the simplicity of the tool, this is a minor gap rather than a serious omission.
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%, so the parameter is already documented, but the description adds meaningful context beyond the schema by clarifying that 'handle' is the product's URL slug and that the base URL is fixed server-side. This helps the agent understand exactly what value to supply.
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 that the tool fetches a single Allbirds product by handle and returns normalized product detail, which is a specific verb+resource combination. It differentiates from plural-oriented siblings like allbirds_products through the explicit 'one ... product handle' phrasing, though it does not name any sibling directly.
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 when to use the tool: when you have a single Allbirds product handle and want normalized details. However, it does not explicitly state when not to use it or mention alternatives like allbirds_products or allbirds_product_recommendations, so the usage guidance is present but mostly implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.