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

Beyond the readOnly and idempotent annotations, the description adds meaningful behavioral detail: grouping URLs by path into H2 sections, deriving titles from slugs, preserving lastmod, adding TODOs where human judgment is needed, and treating a sitemap index as one entry. This helps the agent set accurate expectations for the output.

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 description is dense and informative, but it includes a full JSON-RPC literal for a different tool that is not required to invoke this one. That extraneous block adds clutter and prevents the description from being tightly structured.

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 does a good job explaining what the draft will look like: H2 sections, slug-derived titles, preserved lastmod, TODOs, and sitemap-index handling. It also covers input forms and includes an example, so the main remaining gaps are edge-case error handling and explicit routing among sibling tools.

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%, and all parameters already have descriptive comments and constraints. The description clarifies that xml can be a plain line-separated URL list and provides an example, but this mostly overlaps with the schema rather than adding substantial new parameter semantics.

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 clearly states that the tool consumes a sitemap XML or URL list and produces a draft llms.txt with H2 sections, titles, lastmod, and TODOs. It is specific about the verb and output, though it does not explicitly distinguish this tool from sibling validation/discovery tools, and the embedded JSON-RPC to a sibling muddies the focus.

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 provides usable context: the 'first call' workflow, accepted input formats, an edge case for sitemap indexes, and an example. It does not clearly state when to prefer this tool over alternatives like validate_llms_txt or explain_document, nor any exclusions.

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