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

With no annotations, the description carries the burden and does disclose that this is a fetch operation that returns only summarized group counts, implying a read-only, non-destructive action. However, it does not address error cases, missing robots.txt, or network behavior, so transparency is only partial.

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?

A single sentence captures the core action and output with zero redundant detail. The action is front-loaded and every word contributes.

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 does not explain how the four optional parameters (url, host, json, zone) relate to fetching a robots.txt, which is especially problematic because some schema descriptions (e.g., 'JSON text to validate') seem unrelated to this tool. With no output schema, the format of 'group counts' is also unspecified.

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 the baseline is 3. The description offers no parameter-specific information, but the schema already documents each parameter, so this is acceptable.

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') and resource ('public robots.txt') and specifies the exact output ('return group counts only'), making the tool's purpose unambiguous. It is clearly distinct from the sibling tools, which handle citation, URL normalization, timezone, and JSON validation.

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, nor which inputs are appropriate. The single sentence does not mention any exclusions or context, leaving the agent to infer usage.

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