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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and 'fetch' is consistent with them. The description adds useful workflow context (the handle must be resolved from a catalog/collection tool first) but says nothing further about rate limits or error behavior, so it lands just above baseline given annotation coverage.

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, front-loaded with the primary action and immediately followed by routing advice. No redundant restatement of the name, schema, or annotations.

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?

With an output schema covering return values, annotations covering the safety profile, and a fully documented single parameter, the description supplies everything else an agent needs: the verb, the key, and where to get that key.

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 description coverage is 100% and the single parameter is already documented as a required URL-slug handle. The description's phrasing 'storefront handle' and its pointer to sibling tools adds minor value over the schema, but not format or syntax detail, so the baseline 3 applies.

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?

Specific verb (Fetch) + resource (Brooklinen product detail) + access key (storefront handle), which cleanly distinguishes it from brooklinen_products (list) and brooklinen_product_recommendations (related items). An agent can identify the tool without opening the 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 names the alternatives and the conditions that select them: use brooklinen_products or brooklinen_collection_products to obtain handles, and brooklinen_product_recommendations for related items. This tells the agent both when to use this tool and how to satisfy its prerequisite.

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