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

The description only states that it fetches and returns counts, but does not disclose side effects like network calls, error handling for missing robots.txt, rate limits, or why the nine parameters are present. With no annotations, the description carries the full burden, and it fails to explain the role of parameters like 'city' or 'zone'.

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, efficient sentence with no fluff. However, it is so terse that it omits essential context; while concise, it lacks the structure needed to clarify parameter usage.

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?

The tool has nine parameters but no output schema, and the description explains neither the parameters' relevance nor the expected return format. An agent cannot determine how to supply a robots.txt URL or interpret 'group counts'. The description is wholly inadequate for a tool with this complexity.

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 coverage is 100%, the parameter descriptions are generic and unrelated to fetching robots.txt (e.g., 'city' for a weather hint, 'json' to validate). The tool description does not clarify how any of the nine parameters relate to the stated purpose, making the schema actively misleading.

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 specific resource ('public robots.txt'), and a specific outcome ('return group counts only'). It is concise and clearly distinguishes this tool from siblings like web-fetch or fetch-status by narrowing to robots.txt inspection.

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 given on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a URL, or scenarios where other tools (e.g., web-fetch) would be more appropriate.

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