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

The description discloses that it fetches a public resource and returns only group counts, which gives some behavioral context. However, there are no annotations, so the description carries the full burden; it does not mention failure behavior, response shape beyond counts, or any network-related caveats.

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 front-loaded sentence with no filler words. It earns its place by communicating the core action and output, though it sacrifices necessary parameter guidance for brevity.

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?

Given the eight-parameter schema with irrelevant descriptions, no annotations, and no output schema, the one-sentence description is insufficient. An agent cannot determine which parameter to use, what the 'group counts' return structure looks like, or how errors are handled.

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?

The input schema lists eight parameters, but their descriptions are unrelated to robots.txt (e.g., 'Git ref name', 'JSON text to validate', 'City name for a public weather hint'). The tool description does not explain which parameter identifies the robots.txt URL, making it impossible to invoke the tool confidently from the definition alone.

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 verb and resource: 'Fetch a public robots.txt' and the output is 'group counts only.' This clearly conveys what the tool does. However, it does not distinguish itself from sibling tools like web-fetch or fetch-status, which could also retrieve robots.txt content.

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?

The description implies the tool is for robots.txt group counts but gives no guidance on when to choose this over alternatives such as web-fetch or fetch-status. No exclusion criteria or alternative tool names are mentioned, leaving the AI agent to infer the appropriate context.

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