brooklinen_sitemap_urls

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

No annotations are provided, so the description carries the burden. It discloses that the storefront URL is fixed server-side and that results are capped, which is useful behavioral context. However, it does not disclose pagination behavior, output format, or any rate limits beyond the implied cap.

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 sentences with no wasted words. The core action is front-loaded: 'List Brooklinen sitemap URLs.' The cap and fixed storefront URL are stated concisely, and every sentence 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?

The description is complete for a list-style tool: it names the domain, the child sitemap matching, the cap, and the fixed server-side URL. No output schema exists, but for a URL-list tool the description adequately covers what the agent needs to call it correctly, though it doesn't specify the exact return shape.

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. The description adds meaning by explaining that the type parameter maps to child sitemap types and that results are capped entries, which complements the schema's allowed values and default limit.

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 it lists Brooklinen sitemap URLs, specifically from child sitemaps matching a requested type, and notes the storefront URL is fixed server-side. The verb 'List' plus the resource 'sitemap URLs' is specific and distinguishes it from siblings like brooklinen_sitemaps and 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?

The description implies usage by explaining that the storefront URL is fixed server-side and that the tool returns URLs from child sitemaps matching the requested type. It does not explicitly state when to use this tool versus brooklinen_sitemaps or other sibling tools, but the context of returning URL entries for a specific type provides clear enough usage guidance.

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