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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable context by revealing the fetch behavior, extraction steps, and output format (single text blob in standard markdown). No contradictions with annotations, and it complements them with internal behavior without over-explaining safety.

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 compact and well-structured: first sentence states core purpose and output, second explains the process, third gives use cases. Every sentence adds value, with no fluff or repetition of schema field labels. It is appropriately sized for a simple two-parameter tool.

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 tool with two parameters, high schema coverage, no output schema, and network-fetch behavior, the description covers the key aspects: what it returns, how it works, and when to use it. It could mention error handling or prerequisites (e.g., network access), but the use cases and output description make it sufficiently complete.

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%, so the schema fully documents both parameters. The description reinforces the meaning of 'url' by saying 'any URL' and implies max_links through 'key links', but adds no new parameter-specific detail. 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?

The description clearly states the specific verb 'Generate' and resource 'llms.txt file for any URL', and details the process (fetch, extract, emit markdown). It differentiates from siblings by focusing on producing the file itself rather than auditing or visibility checks, despite the overlapping competitor use case.

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' list explicitly provides three concrete scenarios (client sites, own project, competitor audit), giving clear context on when to use the tool. It does not name alternative sibling tools or state when not to use it, which prevents a perfect score.

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