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

It states the core behavior and output limitation, and parameter descriptions mention discarding/validation, but it doesn't clarify error behavior or why unrelated params exist.

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?

Single sentence, front-loaded with action and output constraint; no wasted 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?

Despite 100% parameter schema coverage, the description is too thin to map purpose to params (e.g., host vs url) and lacks output format/error/usage context, so an agent cannot reliably invoke it.

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?

Because parameter descriptions in the schema cover 100% of params, the tool description adds no parameter-level meaning; it only restates the abstract purpose.

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 action and resource ('Fetch a public robots.txt') and a specific return ('group counts only'), making the tool's purpose reasonably clear despite lacking explicit sibling differentiation.

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?

It provides no guidance on when to choose this over web-fetch/fetch-status or how to supply the target (which param is the robots.txt URL), so invocation decisions are unsupported.

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