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

With no annotations at all, the description carries the full burden of behavioral disclosure. It states the output is 'group counts only' but does not disclose behaviors like whether the fetch is idempotent, error handling on inaccessible robots.txt, rate limits, or caching behavior. 'Group counts only' is a useful constraint, but the description omits important behavioral context for an agent invoking an external network fetch.

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?

One concise sentence with zero waste. It front-loads the action (Fetch) and the constraint (public robots.txt, group counts only). Every word earns its place.

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 is a network fetch with no annotations, no output schema, and four parameters that don't obviously map to the stated purpose. A description this short cannot fully explain how url, host, json, and zone relate to fetching a robots.txt, nor what 'group counts only' means in practice. There is no mention of error behavior, timeouts, or return format. For a tool performing an external fetch with zero structured safety annotations, more context is needed.

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?

Schema description coverage is 100%, so the schema already documents all four parameters: url, host, json, zone. However, these parameters are semantically odd for a robots.txt fetch — url is described as 'HTTPS URL to normalize or cite', json is 'JSON text to validate', and zone is 'IANA timezone name'. The description adds no parameter-specific detail, leaving it unclear how these relate to fetching robots.txt. The baseline of 3 applies due to full coverage, but the mismatch between the schema parameters and the tool purpose is a genuine gap the description could have addressed.

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 return group counts only. This clearly identifies the core purpose, but it does not explicitly distinguish it from sibling tools beyond the inherent uniqueness of the operation. While 'group counts only' adds specificity, the description doesn't mention alternative tools or scenarios.

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 usage by stating 'Fetch a public robots.txt', but provides no explicit guidance on when to use this versus alternatives. It doesn't mention prerequisites like URL normalization or cite behavior. No exclusions or alternative tools are named, leaving the agent to infer when this is the right tool.

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