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

There are no annotations to provide behavioral context, and the description only states the basic action. It does not disclose potential side effects, network usage, error handling, or what happens if the robots.txt is missing or inaccessible.

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 that directly conveys the core functionality without unnecessary verbosity. It is well-structured and easy to parse.

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?

Without an output schema or further explanation, the tool's expected output format is vague ('group counts only'). Moreover, the ambiguous parameter descriptions leave the user unsure how to request a specific robots.txt, making the overall context incomplete.

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?

While the schema covers 100% of parameters, the descriptions are generic and clearly misaligned with the tool's purpose (e.g., 'url' described as 'HTTPS URL to normalize or cite' and 'ref' as 'Git ref name; discarded after the shape check'). These are placeholder-like descriptions that actively mislead rather than clarify how to specify the target robots.txt.

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 tool's purpose: to fetch a public robots.txt and return group counts. It specifies the action (fetch) and the resource (robots.txt), making the intent unambiguous.

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 like fetch-status or normalize-url. The description does not mention any distinguishing conditions or scenarios where this tool is preferred.

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