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

With no annotations, the description must carry the full behavioral burden. It discloses that it returns 'group counts only,' but it does not mention error handling, what happens if robots.txt is unavailable, or that many of its parameters are discarded. The description is silent on the unusual set of parameters, which is a significant transparency gap for a tool with 9 optional inputs.

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 concise sentence with no waste. It front-loads the core action and output. However, it is so terse that it omits critical context, which prevents a higher score for structure.

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 the tool's complexity (9 parameters, no output schema), the description is grossly incomplete. It does not explain why so many unrelated parameters exist, how they are used, what 'group counts' refers to, or any error behavior. An agent cannot reliably call this tool correctly based solely on the description, especially with no annotations or output schema to supplement 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?

Schema description coverage is 100%, so each parameter already has a description in the schema. The tool description adds no additional meaning to the parameters, and it does not explain why parameters like 'city' or 'zone' relate to fetching robots.txt. The baseline of 3 is appropriate since the schema carries the documentation, but the description does not enhance it.

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 a specific verb ('Fetch'), a resource ('public robots.txt'), and an output ('group counts only'). It is clear about the core action and result. However, it does not explicitly differentiate from siblings like 'web-fetch' or 'fetch-status', though the unique focus on robots.txt and group counts distinguishes it implicitly.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list is extensive, and the description provides no conditions, exclusions, or recommended contexts. An agent would have no basis to choose this tool over similar fetch-based tools.

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