brooklinen_pages

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that the tool returns normalized static pages and that the storefront URL is fixed server-side. However, it does not clarify the output shape, whether the operation is read-only, or any rate-limit/auth considerations, which would be valuable for a tool without annotations.

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?

Two taut, front-loaded sentences. The first states the core action and resource; the second adds a useful fact about the fixed URL without padding. Every word earns its place.

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?

Adequate for a simple two-parameter list tool with no output schema. It tells the agent what is returned at a high level ('normalized static pages') but does not describe the fields of those pages. Since there is no output schema, a bit more detail on the return structure would make it complete.

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% — both 'page' and 'limit' are fully documented in the input schema. The description adds no parameter-specific meaning beyond that, so the baseline of 3 is appropriate.

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?

Starts with a specific verb and resource: 'List Brooklinen static pages.' The resource type 'static pages' clearly distinguishes it from sibling tools like brooklinen_page, brooklinen_collections, and brooklinen_products. The addition of 'normalized' and the fixed storefront URL further specify the scope.

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 explicit guidance on when to use this tool versus alternatives like brooklinen_page or brooklinen_sitemaps. The listing behavior is implied by the verb 'List', but there are no stated exclusions or comparisons to sibling tools, leaving the agent to infer selection criteria.

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