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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so safety profile is covered. The description adds behavioral detail: it fetches the page, extracts specific elements, and outputs a text blob. This explains the method and output format beyond the annotations. It doesn't disclose edge cases (e.g., JavaScript-heavy pages) but provides adequate transparency given the annotation coverage.

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 concise and front-loaded: the first sentence states the verb and resource, followed by process details and output format. The 'Useful for' list is structured and each item adds value. No wasted words, and the length is appropriate for the tool's simplicity.

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?

The tool is simple, with schema covering parameters, annotations covering safety, and the description explaining the output format ('single text blob ready to drop at site-root/llms.txt'). It also provides use cases, making it complete for an agent to decide and invoke. No output schema needed since the output is described adequately.

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% for both url and max_links, with clear descriptions in the schema. The description itself does not add extra semantic detail beyond what's in the schema (e.g., it doesn't explain how max_links affects output). Baseline of 3 applies because the schema fully documents parameters.

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 purpose: generate a production-ready llms.txt file for any URL. It specifies the action (generate), resource (llms.txt), and the process (fetches page, extracts title/description/key links, emits markdown). This distinguishes it from sibling tools like ai_visibility_check and scan_competitor_ai_presence by focusing on file generation rather than visibility analysis.

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 provides concrete scenarios (getting a client's site indexed, drafting llms.txt, auditing competitor AI visibility). It implies when to use the tool but does not explicitly exclude alternatives or contrast with sibling tools. Clear context but not explicit '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.