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

No annotations are provided, so the description carries the full burden. It states that it fetches a public robots.txt, implying network access, but it does not disclose failure behavior, timeouts, or what happens when the URL is invalid. It mentions 'group counts only' as the return, but the nature of 'groups' is undefined. The description adds minimal behavioral context.

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, which is concise and front-loaded with the action. However, it is under-specified: it lacks critical details about parameter usage and return semantics. It is concise but not adequately informative.

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 9 parameters, no output schema, and no annotations, the description is far too thin. It does not explain how to invoke it correctly (which parameter to pass), what 'group counts' means, or what the response looks like. The agent would likely be confused about the intended usage given the many discardable parameters. This is inadequate for the tool's 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?

Schema coverage is 100% with all parameters having descriptions, so the baseline is 3. The tool description does not add any meaning beyond the schema; it does not clarify which parameter (e.g., url or host) is actually used for the robots.txt fetch. The schema descriptions themselves are vague for many params (e.g., 'discarded after the shape check'), so the description does not compensate for that ambiguity.

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 clearly states the action: fetch a public robots.txt and return group counts only. This is a specific verb and resource, and it differentiates from sibling shape-checkers like domain-shape and url-ok by indicating a fetch-and-count behavior. However, it omits which input parameter drives the fetch, which is a minor clarity gap.

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 on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or preferred parameters. The agent is left to infer from the parameter list, which is confusing because many parameters are marked as discarded. Without any usage context, the tool is hard to select correctly.

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