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

No annotations are provided, so the description carries the full behavioral burden. It confirms a read-only network fetch and constrains the return to 'group counts only', but it does not explain parsing behavior, error handling, timeout or rate-limit behavior, or what happens for missing or non-robots.txt URLs.

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: verb, target, and output limit all appear immediately. The terseness is a completeness problem, not a conciseness problem.

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 no output schema, no annotations, 9 optional parameters, and a large sibling list, this description is too thin. It does not define what 'group counts' means, what the return value looks like, or how the many 'discarded' parameters relate to the robots.txt fetch.

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 a baseline of 3 applies even though the description itself adds no parameter-level meaning. However, the description never connects its 'robots.txt' behavior to the schema's many generic parameters, and several parameters (ref, city, feed, json, path) appear unrelated to fetching a robots.txt.

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 the action ('Fetch'), the target resource ('public robots.txt'), and the output restriction ('group counts only'), so the core purpose is clear. It does not explicitly say which parameter carries the robots.txt URL, but the intent is unambiguous enough to distinguish it from generic fetch tools.

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 about when to use this tool versus siblings like web-fetch, fetch-status, or normalize-url. The description also does not say whether to pass a URL, host, or something else, nor does it define what counts as 'public'.

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