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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety. The description adds behavioral details beyond annotations: it fetches the page, extracts title/description/key links, and emits standard markdown format. This provides process-level transparency without contradiction.

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 a single paragraph that front-loads the main purpose, then explains the process, and ends with use cases. While not extremely concise, every sentence serves a purpose and adds value. It is well-structured and readable.

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 no output schema and two parameters, the description adequately explains the output format ('single text blob ready to drop at site-root/llms.txt') and lists use cases. It provides enough context for the agent to understand the tool's purpose and result, though omitting potential error cases or edge conditions prevents a perfect score.

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 baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions; it only implicitly references 'url' and 'max_links' in the context of the tool's operation. No additional syntax, format, or constraints are provided.

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's action: generate an llms.txt file for any URL. It uses specific verbs like 'fetches', 'extracts', 'emits', and lists concrete use cases (client site indexing, personal projects, competitor auditing), distinguishing it from sibling tools that focus on visibility checking or scanning.

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 description provides explicit use cases (getting a client's site indexed, drafting for own project, auditing competitors), offering clear context for when to use this tool. However, it does not explicitly mention when not to use it or exclude alternatives among siblings, 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.