brooklinen_store

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

With no annotations provided, the description carries the full burden, and it does this well. It discloses that data comes from credential-free storefront JSON, that the URL is fixed server-side, and that the service may fall back to a *.myshopify.com domain or embedded page data when /products.json is blocked. This gives an agent a realistic picture of the tool's behavior without contradictions.

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 compact and front-loaded, opening with the core purpose, then explaining the source, the no-parameter constraint, and fallback behavior. Every sentence contributes meaningful information and there is no redundant filler.

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 zero-parameter, brand-pinned metadata endpoint, the description is largely complete: it states what is returned, where data comes from, and how fallbacks work. It does not enumerate exact metadata fields or output structure, and since there is no output schema, that leaves some ambiguity, but the tool is simple enough that this is a minor 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 tool has zero parameters, so the baseline is 4, and the description adds extra value by explicitly explaining why no url parameter is accepted: the storefront URL is fixed server-side. This prevents an agent from expecting or attempting to pass a URL and clarifies the invocation contract.

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 uses a specific verb and resource: 'Get Brooklinen store metadata.' It clearly identifies the tool as a brand-pinned wrapper around the generic Shopify store family and states the storefront URL is fixed server-side, which distinguishes it from generic tools like shopify_store and other *_store siblings.

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?

The description gives clear context for when this tool applies: it is specific to Brooklinen, requires no URL parameter, and wraps the generic Shopify store family. It does not explicitly name alternatives or state when not to use it, but the brand-pinning and fixed-URL information make the usage scope reasonably clear.

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