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

The description states it returns group counts, but does not clarify the side effects or how parameters are handled. The parameter descriptions mention 'discarded after the shape check' which implies validation but no details are given, so behavioral transparency is limited.

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 no redundant words. It is well-structured, though it omits critical details; the brevity itself is acceptable.

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?

The description lacks essential context such as what 'group counts' means, which parameter to use, and how the other eight parameters are relevant. Without an output schema, this minimal description is insufficient for an agent to use the tool effectively.

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?

Although the schema has 100% description coverage, the descriptions are misleading and generic (e.g., 'url' described as 'normalize or cite', 'host' as 'Public hostname'). They do not align with the actual purpose of fetching robots.txt, providing incorrect or irrelevant semantics beyond the schema.

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 a public robots.txt' but fails to specify which parameter provides the target URL or host, making it ambiguous. It also doesn't differentiate from sibling tools like fetch-status or web-fetch, so the purpose is only partially clear.

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 provided on when to use this tool versus alternatives. The description does not mention typical use cases, prerequisites, or criteria for selection, leaving the agent without directional information.

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