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

No annotations are provided, so the description carries the full burden. It does disclose two important behavioral facts: the discovery path (robots.txt, falling back to /sitemap.xml) and the cost (2 credits per call). It does not say whether the call truncates to the limit, what happens when no sitemap exists, or whether the result is flat URLs or structured entries.

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, zero filler, and the core action is front-loaded ahead of the cost note. Nothing is repeated from the title or schema.

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?

There is no output schema, so the description must describe the return, and it does at a high level ('list the page URLs'). Combined with the disclosed discovery mechanism and per-call cost, an agent has enough to select and call it, though truncation behavior for 'limit' is still unspecified.

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 coverage is 50%: 'site' is documented ('Site root, e.g. https://example.com') while 'limit' has no description, though its default of 500 and maximum of 2000 are visible in the schema. The description contributes no parameter meaning at all, so it neither compensates for the gap nor adds value beyond the schema.

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 and resource ('find a site's sitemap... and list the page URLs') and even names the discovery mechanism (robots.txt or /sitemap.xml). It does not differentiate itself from close siblings like crawl_site, extract_links, or check_urls, so an agent must infer the boundary itself.

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?

Usage is implied by the name and description (fetch a sitemap for a site root, not crawl or scrape it), but there is no explicit when-to-use guidance and no named alternative. With ~100 sibling tools including crawl_site and site_audit, an explicit contrast statement would be valuable and is absent.

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