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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds behavioral context by stating it 'fetches the page' and 'extracts' content, which implies network access and processing. It also explains the output format, though it does not detail error handling or rate limits. This adds value beyond the annotations.

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, with three sentences. The first sentence front-loads the core purpose, the second describes the underlying process and output, and the third lists practical use cases. Every sentence adds meaningful information without fluff.

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?

Given the tool's simplicity (2 params, no output schema), the description covers all necessary aspects: purpose, process, output, and use cases. It explicitly states the output is a 'single text blob', which compensates for the lack of an output schema. The annotations cover safety and side-effect context, making this description complete for an agent.

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 additional parameter-specific details beyond what the schema provides for 'url' and 'max_links'. It indirectly references the extraction behavior but does not clarify parameter syntax or defaults beyond the schema.

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 function: generating a production-ready llms.txt file for any URL. It specifies the process (fetch, extract title/description/key links, emit markdown) and the output (a text blob). This distinguishes it from sibling tools like scan_competitor_ai_presence, which focus on visibility checking rather than file generation.

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 clear contexts for use, such as getting a client's site indexed, drafting llms.txt for a project, or auditing a competitor. It does not explicitly mention alternative tools or state when not to use this tool, but the use cases are sufficiently clear to guide an agent.

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