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

No annotations are present, so the description must carry the full behavioral burden. It specifies that only group counts are returned and restricts itself to public robots.txt, but it doesn't disclose HTTP mechanics, side effects, or how the parameter set interacts with fetching. The sparse wording leaves important behavioral traits implicit.

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, compact sentence that captures the core behavior with no filler. Each word earns its place, and the 'only' qualifier sets clear expectations about output granularity.

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?

With nine parameters, no output schema, and zero annotations, the description is far too thin. An agent has no way to know which parameter drives the fetch, how the 'group counts' are structured, or what happens to the other eight parameters. The mismatch between the simple robots.txt claim and the generic-looking parameter list creates serious ambiguity.

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 the baseline is 3 even without additional parameter info in the description. The description doesn't map any of the nine parameters to the robots.txt fetch—it's not clear whether 'url' or 'host' is used—so it adds no value beyond the schema itself.

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 clear action (fetch) and resource (public robots.txt) and specifies the output shape (group counts only). It doesn't explicitly differentiate from sibling fetch-like tools, but the purpose is obvious from the name and description.

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 over siblings like web-fetch or fetch-status. It doesn't mention the required input (which parameter supplies the robots.txt URL), nor any preconditions or alternatives, leaving invocation decisions entirely to the agent.

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