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

With no annotations, the description must carry the behavioral burden, but it only states that it fetches robots.txt and returns group counts. It does not disclose network behavior, error handling, how the URL is derived from parameters, or what 'group counts' means. The parameter descriptions suggest unrelated discards, adding confusion.

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 fluff, front-loaded with the action. It earns a high score for efficiency, though the extreme brevity contributes to the lack of behavioral detail.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is grossly insufficient. It fails to explain how parameters map to the robots.txt fetching, the return format, error conditions, or any operational details, making it nearly impossible for an agent to call correctly.

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 schema provides 100% coverage with individual parameter descriptions, but they are unrelated to robots.txt (e.g., 'Git ref name; discarded after the shape check'). The tool description does not connect any parameter to the robots.txt URL, so it adds no value and the schema itself is 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 clearly states a specific verb and resource: fetch a public robots.txt and return group counts. This distinguishes it from generic fetch tools like web-fetch. However, it does not explicitly contrast with siblings or mention the output format, so it falls short of a perfect 5.

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 versus alternatives like web-fetch or fetch-status. The description does not state any preconditions, use cases, or exclusions, leaving the agent to infer appropriate usage.

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