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 genuine behavioral detail beyond that: results are 'capped' and each handle is derived from the URL path with tracking/variant query parameters stripped — a real data-transformation trait an agent would not otherwise know.

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 resource definition and followed by the most actionable detail (handle derivation and its link to quince_product). No filler; the dense second sentence is dense for a reason.

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 values need not be described. Still, with zero schema coverage and no enums, the agent has no idea which 'type' strings are legal — a notable gap for a type-filtered tool, partially offset by the helpful product/handle workflow note.

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 0%, so the description carries the burden. It partially compensates by explaining the semantics of the 'type' filter (e.g. products) and the derived handle value, but it never enumerates the valid type values nor explains what 'limit' does beyond the word 'capped'.

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 names the specific resource (capped URL entries from Quince's own sitemaps) and the scoping filter (matching the requested type), which is enough to separate it from a plain sitemap-listing tool. It stops short of explicitly contrasting itself with the sibling quince_sitemaps, so the differentiation is implied rather than stated.

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?

It gives one concrete chained-use hint: for type=products the returned handle is exactly what quince_product's handle parameter expects. However, it never states when to prefer this tool over quince_sitemaps, quince_navigation, or quince_search, and gives no guidance for non-product types.

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