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

There are no annotations, so the description carries the full behavioral transparency burden. It does mention that only group counts are returned, which is a useful output-scope disclosure, but it omits network failure behavior, handling of missing robots.txt files, rate limits, or side effects. This is insufficient for a network-touching tool.

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 single sentence is sharply front-loaded with the explicit action and resource, with no filler or repetition. However, the extreme brevity comes at the expense of disambiguation and parameter guidance, though for pure conciseness it works.

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 output schema, no annotations, 9 parameters, and 28 siblings with overlapping capabilities. The one-sentence description makes no attempt to explain which parameter is relevant, what the output shape looks like, or how this differs from the many network fetching siblings, making it incomplete for confident use.

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 9 parameters whose descriptions feel unrelated to robots.txt: 'url' is described as 'HTTPS URL to normalize or cite', while others like 'ref', 'city', and 'zone' describe discarded or validation-only values. The tools description adds no mapping between 'robots.txt' and any specific parameter, so an agent cannot reliably know which parameter to populate.

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 concrete verb and resource: 'Fetch a public robots.txt and return group counts only.' This distinguishes it from generic fetching siblings like web-fetch or fetch-status because it targets robots.txt specifically. 'Group counts' is slightly ambiguous, but the main purpose is 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 usage context is given. The description never says when to use this over siblings like web-fetch, fetch-status, browser-url-ok, or normalize-url, and there are no exclusions or prerequisites. An agent is left to infer the appropriate scenario.

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