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 that results are 'capped' and that the storefront URL is fixed, which is useful context, but it does not go further on pagination, rate limits, or URL record shape. Moderate value over 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 tight sentences, front-loaded with the action and resource, second sentence carrying the routing guidance. No filler or redundancy.

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 not needed. The description covers the selection mechanism, the fixed storefront, and the prerequisite tool, which is sufficient for this simple list tool; only deeper behavioral detail (pagination/limits semantics) is absent.

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 both `type` (with its allowed enum values) and `limit` (default 50, max 250) are fully documented in the schema. The description only alludes to `type` as the selector and 'capped' as the limit concept, adding no syntax beyond what the schema already provides. Baseline 3 is correct.

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 Kylie Cosmetics child sitemap), and names the mechanism of selection (by `type`). It explicitly sets itself apart from the sibling kyliecosmetics_sitemaps, so an agent can distinguish the two without opening a 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?

Routes the agent clearly: 'Use kyliecosmetics_sitemaps to discover sitemap types', establishing the prerequisite and the alternative tool. It stops short of stating exclusions (when NOT to use this tool), so it lands at a strong 4 rather than a full 5.

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