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

No annotations are provided, so the description carries the full burden. It does disclose that it returns only group counts, which is a behavioral constraint. However, it doesn't mention error handling, what happens if robots.txt is missing, authentication requirements, or any side effects. The description is minimal and leaves many behavioral aspects unaddressed.

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 sentence that is concise and front-loaded with the core action. It wastes no words and is easy to read.

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 tool appears simple, but the description lacks essential context: it doesn't define what 'group counts' means, doesn't indicate which parameter corresponds to the robots.txt URL, and doesn't explain why the other parameters (json, zone) exist. With no output schema and no annotations, the description is incomplete and likely to mislead an agent into incorrect invocation.

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 has 100% description coverage for parameters, which normally warrants a baseline of 3. However, the tool description doesn't explain how the parameters relate to fetching robots.txt. The parameters include url, host, json, and zone, but only url (and possibly host) seem relevant, and the url description ('HTTPS URL to normalize or cite') is generic and doesn't clarify its role here. The description fails to add meaning or guidance beyond the schema, making it insufficient for an agent to know which parameters to use.

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 ('fetch'), a resource ('public robots.txt'), and an outcome ('return group counts only'). It clearly indicates what the tool does, though it doesn't explicitly distinguish it from sibling tools like 'normalize-url' or 'validate-json', which is a minor gap.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention conditions, exclusions, or sibling tools that might be more appropriate. The only implied usage is that you need group counts from a robots.txt, but no explicit context is provided.

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