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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that this is a public fetch and that only group counts are returned, but it does not explain network behavior, failure modes, redirect handling, or what happens when no robots.txt exists.

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. It efficiently states the action, the resource, and the output restriction.

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 optional parameters, no output schema, no annotations, and an ambiguous mapping between parameters and the robots.txt task, the bare one-sentence description is not enough for an agent to reliably invoke the tool. It lacks parameter selection guidance, return-value details, and error behavior.

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 schema description coverage is 100%, the parameter descriptions are generic and not tied to robots.txt. An agent cannot tell from the schema or description whether to pass 'host', 'url', or 'path' to identify the target, and fields like 'city', 'feed', and 'json' appear irrelevant to the tool's stated 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 verb and resource ('Fetch a public robots.txt') and a precise output ('return group counts only'). This clearly distinguishes it from sibling tools like web-fetch or fetch-status, which would return full content or status rather than summarized group counts.

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 gives no guidance about when to choose this tool over alternatives such as web-fetch, normalize-url, or domain-shape. It does not mention what input should be provided or when the tool should not be used.

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