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

No annotations are present, so the description carries the transparency burden. It discloses that a network read occurs ('Fetch'), that no auth is expected ('public'), and that the full body is not returned ('counts only'). It does not cover failure modes, but the core behavioral contract is clear.

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 filler. Action, resource, and output scope are all present and each word contributes meaning.

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?

Given nine optional parameters, no annotations, and no output schema, a one-line description is too thin. It omits which parameter carries the robots.txt URL/host, what 'group counts' means structurally, and how failures are reported, so correct invocation depends on inference.

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?

All nine parameters already have schema descriptions, so the baseline is 3, and the tool description adds no parameter-specific meaning. It never maps the robots.txt target to either `url` or `host`, leaving the agent to infer which field 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 names a concrete action ('Fetch'), a precise resource ('public robots.txt'), and a constrained output ('group counts only'). This clearly distinguishes it from siblings like web-fetch or fetch-status, which would return full content or status information.

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 word 'only' provides clear context that this tool is for count-level results rather than full robots.txt inspection. It does not explicitly name alternatives or state when-not-to-use, but the count-only framing gives the agent a solid usage signal.

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