brooklinen_product_recommendations

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the disclosure burden and does more than restate the purpose. It discloses that output is normalized, that a handle is resolved server-side to a Shopify product id, and that the storefront URL is fixed, so the agent is not misled about configurability.

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 front-loaded with the core action and stays compact at three sentences. Each sentence adds information, though the first sentence is slightly redundant with the tool name and the fixed-storefront note could have been folded into the second sentence.

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 single-handle recommendation tool with three well-documented parameters, the description supplies enough context to select and invoke it correctly: what it returns, what the handle is, and how resolution works. It does not enumerate output fields, but no output schema exists and the agent is at least told the products are normalized.

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 baseline is 3; the description adds real value by clarifying that 'handle' is a Brooklinen route handle resolved to a Shopify product id rather than a raw product id. The limit and intent parameters are already well documented in the schema.

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 names a specific operation and resource ('List Brooklinen product recommendations') and further scopes it to a single product handle with normalized output. This clearly separates it from sibling tools such as brooklinen_product or brooklinen_products, which serve single-product or full-catalog purposes.

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 makes the invocation context clear: use it when product recommendations for one Brooklinen handle are needed. It does not explicitly name alternatives or when-not-to-use cases, but the single-handle constraint provides enough directional guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.