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

Annotations cover read-only and open-world, so safety is known. The description adds nothing about pagination semantics, catalog completeness, ordering, or rate behavior for a paged product listing. No output schema caveat needed, but zero added context for a paginated tool.

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?

One short front-loaded sentence with no waste. Slightly under-specified rather than over-long, but structurally clean.

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 catalog-listing tool surrounded by a dense family of Brooklinen siblings, the description omits the routing information an agent needs. The output schema existence lowers the burden on return values, but scope and sibling differentiation are missing.

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%; both page and limit are fully documented in the schema, so baseline 3 applies. The description adds no parameter-level meaning beyond what the schema provides.

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?

States the resource (Brooklinen storefront products) and pins the source domain, so an agent knows it lists products. But it gives no scope detail (full catalog vs. filtered) and does not distinguish itself from the sibling brooklinen_product (singular detail tool) or brooklinen_collection_products.

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?

No when-to-use, no alternatives named, no exclusions. An agent must guess whether to call this or brooklinen_product/collection_products/search_suggest based on the name alone.

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