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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose the network fetch of a public resource and the output restriction to 'group counts only', but it fails to mention which input parameter drives the fetch, what happens on missing robots.txt, or network/error behavior.

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 zero filler. It states the action, target, and output constraint efficiently.

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 network-fetching tool with no output schema and a poorly aligned generic input schema, the description is too minimal. It does not specify which parameter to populate, what 'group counts' means in the response, or error handling behavior, making successful invocation uncertain.

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?

The input schema has high coverage, so the baseline is 3, but the description adds no mapping between its purpose and the eight parameters. The schema descriptions like 'HTTPS URL to normalize or cite' and 'discarded after the shape check' do not clarify which parameter should hold a robots.txt URL, leaving agents to guess whether to use url, host, or another field.

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 ('Fetch'), resource ('public robots.txt'), and output ('group counts only'), which clearly distinguishes it from generic siblings like web-fetch or fetch-status. However, 'group counts' is slightly ambiguous and no explicit contrast with sibling tools is provided.

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?

There is no guidance on when to use this tool versus alternatives such as web-fetch, fetch-status, or normalize-url. The description implies a use case but lacks any context, prerequisites, or conditions for selection.

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