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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds that results are 'capped' and that the store URL is fixed (no store parameter needed), which is useful context, but it does not discuss ordering, pagination, or rate behavior beyond the schema's max.

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, no filler, with the scoping constraint front-loaded and the alternative tools relegated to the routing sentence. Every clause carries information.

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?

An output schema exists, so return-format details are unnecessary, and annotations carry the safety profile. Combined with the clear routing and the fixed-store note, the definition is nearly complete; only secondary behaviors like ordering/pagination are unaddressed.

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 `type` (with its allowed values and default) and `limit` (default 50, max 250). The description adds only that `type` selects the child sitemap section, which is marginal over the schema. Baseline 3 applies.

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 (List) and resource (capped URL records from a Fashionphile child sitemap) with the distinguishing scope that the store URL is fixed and selection is by `type`. It also names the two sibling tools it is not, so an agent can disambiguate without opening the 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?

Explicitly routes the agent: use fashionphile_sitemaps to discover child sitemap types, or fashionphile_pages for static-page listings. Both alternatives and the condition that selects them are spelled out.

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