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

Annotations already declare readOnly/idempotent/destructive hints. The description adds process details (fetches the page, extracts title/description/key links, emits standard markdown) and output format (single text blob for site-root/llms.txt), which goes beyond the annotations and gives the agent a clear behavioral model.

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 three sentences, front-loaded with the core purpose, and the use-case list adds practical value without unnecessary length. Every sentence contributes meaning, and the formatting is clean.

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?

Since there is no output schema, the description's explanation of the output ('single text blob ready to drop at site-root/llms.txt') is critical and well-provided. Combined with full parameter descriptions and strong annotations, the description is complete for agent use.

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 descriptions cover both parameters (url and max_links) with clear explanations, including default and max for max_links. The description doesn't add additional parameter-level detail beyond mentioning 'any URL', so baseline 3 is appropriate for full schema coverage.

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 the tool generates a production-ready llms.txt file for any URL, using a specific verb (generate) and resource (llms.txt file). It distinguishes from siblings by focusing on file generation rather than visibility checks or scanning, and the use cases further clarify its purpose.

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?

The 'Useful for' section explicitly lists three clear contexts: getting a client's site indexed, drafting llms.txt for a project, and auditing competitors. It doesn't name alternatives or exclusion criteria, but the contexts are specific enough to guide selection.

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