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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine behavioral context beyond that: the storefront URL is fixed server-side and empty result pages return 200 with an empty products array. That empty-page behavior is a non-obvious trait an agent needs. It does not describe pagination termination or ordering, keeping it below 5.

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?

Purpose and the key constraint (fixed storefront URL) are front-loaded, and the sentences are short and readable. The verbatim repetition of the two parameter descriptions is mildly redundant with the schema but not enough to disrupt the structure.

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-value explanation is not required, and the description still notes the empty-array response shape. With 100% schema coverage and annotations handling safety, the definition is nearly complete; only pagination/ordering behavior is left unstated.

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 description simply restates the schema wording for limit and page verbatim ('Maximum products to return. Default 50, maximum 250.' / '1-based page number, default 1.'). It adds no syntax, interaction, or edge-case meaning (e.g., behavior when page exceeds range), 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?

The description names a specific verb and resource ('Returns normalized products from Brooklinen's public product catalog') and explicitly routes the agent to brooklinen_product for single-product lookups. It does not, however, differentiate itself from brooklinen_collection_products or the other catalog-listing siblings, so it stops short of a clean 5.

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?

It says to use brooklinen_product to get a single product, which is one useful alternative, but gives no guidance on when to prefer this full-catalog listing over brooklinen_collection_products, brooklinen_search_suggest, or brooklinen_sitemaps. Usage is only implied (browse the whole catalog).

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