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

The description mentions 'Fetch' implying a read operation, but does not disclose any side effects, error conditions, or the fact that it may require network access. With no annotations, this minimal description leaves too much unspecified.

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 main description is a single, concise sentence that is easy to parse. However, it omits critical usage details, and the overall structure is undermined by the irrelevant parameter descriptions.

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 is far too incomplete: it does not specify which parameters are required, how group counts are computed, what output format is returned, or how errors are handled. Without an output schema or annotations, this ambiguity is critical.

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?

Despite 100% schema coverage, the parameter descriptions are copied from unrelated tools (e.g., 'JSON text to validate' and 'IANA timezone name') and do not explain how url, host, json, or zone relate to fetching or parsing robots.txt. The descriptions are misleading.

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 action (fetch robots.txt and return group counts), but the parameter list mismatches the purpose (includes json and zone which are irrelevant), creating confusion about the tool's actual function.

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 given on when to use this tool compared to siblings like normalize-url or validate-json. The intended use case and selection criteria are entirely absent.

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