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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'fetch' and 'return group counts' without disclosing which parameter selects the URL, error behavior, rate limits, or that many parameters are discarded. The schema suggests a generic shape-checker, directly contradicting the stated purpose.

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 the action front-loaded. However, it is under-specified and omits essential details, so while concise, it sacrifices informativeness.

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 optional parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain which parameter is the robots.txt URL, what 'group counts' means, how parameters interact, or any expected behavior. An agent cannot correctly invoke this tool based on the description.

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?

All 9 parameters have descriptions in the schema, but these descriptions are unrelated to the stated purpose (e.g., 'city' for weather, 'json' for validation, 'path' for file check). The description does not explain how any parameter maps to fetching a robots.txt, so the parameter semantics add no meaningful guidance for this tool.

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 clear action ('Fetch a public robots.txt') and a resource, but it does not distinguish from sibling tools like web-fetch or fetch-status, and the parameter schema (city, zone, json, etc.) contradicts the stated purpose, making the tool's actual function ambiguous.

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, no prerequisites, and no exclusions. The description provides no context for selection among the 26 sibling tools.

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