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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a read-only network fetch and a narrowed output, but omits details such as error behavior, redirect handling, rate limits, or whether a missing robots.txt results in empty counts.

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 front-loaded sentence with no wasted words. 'Group counts only' usefully scopes the output and the sentence structure carries no repetition or filler.

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, the return value is only vaguely defined as 'group counts', and the input ambiguity around four optional, unrelated parameters leaves meaningful gaps. It is adequate for a narrow utility, but parameter mapping and edge-case behavior are insufficiently covered.

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?

Although schema coverage is 100%, the parameter descriptions are generic and appear cloned from sibling tools ('JSON text to validate; discarded after the check', 'IANA timezone name'). The description never maps the robots.txt fetch to the 'url' parameter or states that the other parameters are irrelevant, and no parameters are required, making correct invocation ambiguous.

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 states a specific verb and resource ('Fetch a public robots.txt') and a specific output ('group counts only'). This clearly distinguishes the tool from sibling utilities such as normalize-url or validate-json.

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 core use case is implied by the wording, but the description gives no explicit guidance on when to choose this tool over alternatives, nor any exclusions. It also does not mention what to do when a site lacks a robots.txt or when a different inspection tool would be more appropriate.

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