brooklinen_search_suggest

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

With no annotations provided, the description carries the full burden. It discloses that the endpoint is 'credential-free' (no auth needed) and that the storefront URL is fixed server-side (no configuration needed), adding real behavioral context. It does not cover rate limits, error behavior, or response structure, but it goes well beyond a bare statement.

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: a front-loaded one-line summary, a second sentence adding return types and the source endpoint, and a third noting a key constraint. Every sentence earns its place with no fluff.

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 read-only suggest tool with fully documented parameters and no output schema, the description provides enough to invoke it correctly: purpose, return categories, auth model, and URL constraint. It stops short of describing the exact response shape, which is a minor gap given the simplicity of the tool.

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%, so the baseline is 3. The description's mention of 'products, collections, and query suggestions' mirrors the allowed values of the 'types' parameter but adds no new semantic detail beyond what the schema already 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?

The description states a specific action ('Get') and resource ('Brooklinen search suggestions'), and enumerates the returned content (products, collections, and query suggestions). This clearly distinguishes it from Brooklinen product/collection retrieval siblings such as brooklinen_products 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?

There is no explicit statement of when to use this tool versus alternatives or exclusions. The phrases 'predictive search' and 'suggestions' imply a search-as-you-type use case, but no alternative tools are named, so usage guidance is only implicit.

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