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

With no annotations, the description carries the full burden. It honestly states that only group counts are returned, which sets output expectations, but it does not disclose potential failure modes, network dependency, or behavior when robots.txt is missing/malformed.

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?

A single, front-loaded sentence with no filler. It packs the action, resource, and output restriction into ten words.

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 has no annotations, no output schema, and four optional params that are not tied to the described operation. The description is too sparse to let an agent confidently call it correctly; it omits which param supplies the target, expected return format details, and error behavior.

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 coverage is 100%, so a baseline of 3 is warranted, but the description adds nothing about how the four parameters map to the robots.txt operation. Worse, the parameter descriptions ('HTTPS URL to normalize or cite', 'JSON text to validate') appear mismatched with the stated purpose, and the description does not resolve that confusion.

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 names a specific verb ('Fetch'), a specific resource ('public robots.txt'), and an exact output ('return group counts only'). This cleanly distinguishes it from the sibling tools like citation, validate-json, and normalize-url, making its purpose clear.

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?

No guidance is provided on when to use this tool versus the siblings. The description simply states what the tool does, leaving the agent to infer the appropriate context and offering no exclusions or alternatives.

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