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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read-only network fetch and a restricted output, but it does not disclose which parameter supplies the robots.txt URL, failure modes, rate limits, or what 'group counts' means. It also does not mention that many schema parameters appear to be discarded or unrelated.

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. It is concise and readable. However, it is under-specified for a tool with 9 parameters, so it does not earn a 5.

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 optional parameters, no annotations, and no output schema—the description is not complete enough. It fails to identify the relevant input parameter, explain the return format of 'group counts', or clarify behavior when multiple parameters are supplied. An agent would struggle to invoke 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%, which normally sets a baseline of 3, but the schema descriptions describe unrelated operations such as normalizing URLs, weather hints, timezone names, and search-length checks. The description does not map any parameter to the robots.txt URL. With 9 optional parameters and no required ones, an agent cannot determine what to pass.

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 uses a specific verb ('Fetch'), a specific resource ('public robots.txt'), and a precise output ('return group counts only'). This clearly distinguishes it from generic fetch tools like web-fetch or fetch-status and from shape-check siblings.

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 about when to use this tool versus alternatives such as web-fetch, fetch-status, or domain-shape. No exclusions, conditions, or alternative tool names are mentioned. The only implied usage is 'public robots.txt', but that is not enough to route an agent correctly.

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