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

No annotations are provided, so the description carries the full burden and does so: read-only, passive, no crawling or brute-forcing, and it carefully bounds its own behavior ('for the one sitemap fetched' — not all sitemaps). It discloses that only two public files are touched, which is meaningful operational context.

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 core action and the recon value are front-loaded, and every clause carries information. It is a dense single paragraph with several parentheticals, which is slightly heavier than necessary but not padded.

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?

With no output schema, the description enumerates the return payload precisely: disallowed paths, crawl-delay, sitemap URLs, plus index status, <loc> count, and sample entries. Combined with the explicit negative scope, an agent has everything needed to call and interpret the result.

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?

With one parameter at 100% schema description coverage, the schema already documents 'domain' including the 'Domain or URL, e.g. example.com' example. The description adds no format, normalization, or scope detail beyond that, so baseline 3 is appropriate.

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 pair ('passively read a site's robots.txt and the sitemap it points to') and enumerates exactly what is returned. It also explicitly distinguishes itself from scan_site and active content discovery, so an agent can pick it apart from siblings 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 scopes usage to passive reading of two owner-published files and names the alternative ('that active content discovery is scan_site/Astur's job'). It also states what the tool does NOT do (crawl, guess, brute-force), giving both when-to-use and when-not-to-use guidance.

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