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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful constraint that it returns rows from a single child sitemap, but says nothing about pagination, rate limits, or result shape beyond what the output schema provides.

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 zero waste; the purpose is front-loaded and the sibling routing follows immediately. Nothing repetitive or padded.

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?

With an output schema present, return values need not be explained, and annotations cover the read-only/open-world profile, so the description is largely complete. One residual gap: it frames the result as coming from 'one child sitemap' but no parameter identifies which sitemap, leaving the type-to-sitemap relationship to inference.

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 type and limit fully. The phrase 'by type' gestures at the type parameter but adds no syntax or semantics beyond the schema's allowed-values list. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Fetch) plus resource (sitemap URL record rows) and scope (one Cole Haan child sitemap, filtered by type). It also names colehaan_sitemaps as the sibling that discovers sitemaps, letting an agent distinguish this from the discovery tool without opening either schema.

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 explicitly routes the agent: use colehaan_sitemaps first to discover sitemap URLs, then use this tool for the rows, and points to colehaan_pages / colehaan_collections for specific browse catalogs. The workflow and alternatives are clear, though it doesn't phrase a crisp when-not condition (e.g. when to prefer this over the pages/collections tools for the same URL).

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