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

There are no annotations, so the description must carry the full behavioral burden. It reveals that the operation is a public, read-only fetch and that output is limited to group counts, but it does not explain failure behavior, redirect handling, or why the input schema contains many unrelated parameters with 'discarded after' semantics.

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. Every word contributes to the action and output scope.

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 tool with seven input parameters and no output schema or annotations, the description is too thin. It does not explain how the schema relates to 'inspect-robots', what 'group counts' means exactly, or how to invoke the tool correctly, leaving too much to 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?

Although every parameter has a schema description, those descriptions are generic and often mention unrelated concerns like normalizing URLs or discarding inputs. The description never maps any of the seven parameters to the robots.txt fetch, so an agent cannot confidently tell whether to pass 'url' or 'host'.

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 verb ('Fetch'), a distinct resource ('public robots.txt'), and a precise output ('return group counts only'). This makes the tool's purpose unambiguous and separates it from generic sibling tools like web-fetch or fetch-status.

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 description implies when to use the tool: when robots.txt group counts are needed rather than full content. However, it does not explicitly state when not to use it, and it names no alternative tools, so the routing guidance is only implicit.

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