brooklinen_collections

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

With no annotations, the description carries the behavioral burden and does add useful context: data is normalized, the storefront URL is fixed server-side, and valid empty pages return 200 with an empty collections array. These are genuinely informative behavioral details. It does not disclose authentication, rate limits, or error behavior beyond empty pages, but for a simple read-only list tool this is reasonably transparent.

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?

The description is concise and well-structured: three short sentences, with the core purpose front-loaded, followed by useful normalization/source context and an edge-case behavior. No sentence is redundant or wasteful.

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 collections list with no output schema, the description covers the essential operational details: source, normalization, fixed storefront URL, and empty-page behavior. It is complete enough for an agent to invoke the tool correctly, though it could optionally describe what fields a collection contains.

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 schema already documents both parameters clearly. The description adds no additional meaning about page or limit beyond what the schema provides, satisfying the baseline without exceeding it.

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 clearly states the verb and resource: "List Brooklinen collections." It also clarifies it returns normalized collections and notes that empty result pages return an empty array, which makes the resource unambiguous. However, it does not explicitly differentiate this tool from related sibling tools like brooklinen_collection_products or brooklinen_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 guidance on when to use this tool versus alternatives. The description does not mention when to prefer brooklinen_collections over brooklinen_collection_products or any other sibling, nor does it state any prerequisites. The usage context is only implied by the word "List."

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