brooklinen_products

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully explains that products are normalized, the storefront URL is fixed server-side, and valid empty result pages return 200 with an empty products array. This goes beyond a minimal description by covering an important edge case.

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?

Three concise sentences with the primary action front-loaded. Each sentence contributes distinct information: what is listed, the source catalog, the fixed URL behavior, and empty-page handling. No filler or redundancy.

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 simple paginated catalog-list tool, the description is mostly complete: it identifies the source, explains the fixed endpoint, and documents empty-page behavior, with pagination covered in the schema. The absence of an output schema leaves product fields unspecified, but that is a structural limitation rather than a description gap.

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?

The input schema already covers both parameters fully with descriptions for page and limit, including defaults and the 250 cap. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score 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 opens with a specific verb and resource: 'List Brooklinen products.' It clearly identifies the source as Brooklinen's public product catalog. It does not explicitly differentiate itself from sibling tools like brooklinen_collection_products or brooklinen_product, so it misses the top score.

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?

Usage context is implied rather than explicit: listing products is self-explanatory, and the notes about the fixed server-side URL and empty-result behavior provide some operational context. However, there is no guidance on when to choose this over brooklinen_product, brooklinen_collection_products, or brooklinen_search_suggest.

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