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

There are no annotations, so the description must carry full behavioral disclosure. It says 'fetch a robots.txt' but then mentions 'return group counts only' without explaining how the many other schema parameters are handled (several are marked 'discarded'). The description is misleading because the actual behavior is not clearly disclosed and contradicts the broad parameter set.

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 sentence, which is concise, but it is under-specified. It lacks necessary detail about parameters, behavior, and output, making it insufficient rather than appropriately concise. The brevity does not add value because it omits critical information.

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 9 parameters, no output schema, and no annotations, the description must provide substantial context to be usable. It fails to explain the actual function, which parameter is relevant, what 'group counts' means, or how the tool interacts with the various schema fields. The description is wholly inadequate for an agent to call this tool correctly.

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 description coverage is 100%, but the descriptions are generic and not aligned with the tool's stated purpose. For example, 'url' is described as 'HTTPS URL to normalize or cite,' which does not mention robots.txt. The description itself adds no clarification about which parameter is the primary input, leaving the agent uncertain about how to invoke the tool correctly.

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 states 'Fetch a public robots.txt and return group counts only,' but the input schema contains 9 unrelated parameters (e.g., city, json, zone) with no clear indication of which parameter actually targets the robots.txt. This is confusing and does not clearly distinguish the tool from siblings like fetch-status or web-fetch, which also deal with URLs.

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?

No guidance is provided on when to use this tool versus any alternative. The description does not mention prerequisites, exclusions, or context for selection. Given the schema's mix of unrelated parameters, an agent has no basis to decide when to call this tool.

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