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

With no annotations at all, the description carries the full burden and does a solid job: it discloses the 5000-URL ceiling, that the fallback crawls homepage links when no sitemap is found, that billing occurs only on success, and the exact price and payment rail (x402, USDC on Base). It stops short of stating wallet/auth prerequisites, rate limits, or error behavior beyond the success-charging rule.

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?

The definition is dense and front-loaded, leading with the resource and its sources before moving to output fields, fallback, and pricing. Every clause carries information, though the parenthetical "(indexes, gzip, text)" and the pricing sentence make it a tightly packed run-on that could be split for readability.

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?

For a four-parameter read tool with no output schema, the description covers what is returned (URLs plus lastmod/changefreq/priority), the volume cap, the fallback path, and the payment model, which is what an agent needs to invoke it responsibly. Missing only edge behavior such as failure responses and any payment prerequisites.

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 100%, so the schema already documents all four parameters, and the description only loosely restates two of them ("optional keyword filter" for contains, "homepage-link fallback" for fallback). The one genuinely additive fact is the 5000-URL server-side cap, which contextualizes the limit parameter's 500 default.

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 a specific verb and resource ("list every page URL on a site") and enumerates the discovery sources it draws from (robots.txt, XML sitemaps, indexes, gzip, text). Siblings are unrelated tools, so an agent can tell instantly what this does and that it does not overlap with contacts, markdown, or metadata.

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 context is implied rather than stated: the mention of a homepage-link fallback tells the agent it still returns something when no sitemap exists, but there is no explicit "use this when..." or "do not use this for..." guidance. No alternatives are named, which is partly because no sibling performs URL discovery.

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