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

The description only says it fetches and returns group counts; it does not disclose behavior around ignored/discarded parameters, URL/host handling, error cases, or output format. With no annotations provided, the description carries the full burden and doesn't meet it.

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 sentence with no filler, front-loading the verb and resource. Every word earns its place.

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?

For a tool with seven parameters and no annotations, the one-line description is far from complete: it omits how to specify the target URL/host, what 'group counts' means, and what the response looks like. The agent is left with too much ambiguity to call it reliably.

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?

The input schema has seven parameters, but none of their descriptions mention robots.txt, and the description provides no mapping to the correct parameter. Several parameters are described as discarded or unrelated to robots (city, feed, json, path), so the agent cannot determine what to pass for the target site.

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 clear resource ('a public robots.txt'), and a precise output ('return group counts only'). It is distinct from generic siblings like web-fetch or fetch-status because it names robots.txt inspection as its scope.

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 instead of siblings such as web-fetch, fetch-status, or normalize-url, nor any exclusions. Usage is only implied by the name and the short description, leaving the agent to infer the calling context.

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