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

With no annotations, the description carries the full burden of behavioral disclosure. It states a network fetch and count-only output, but does not disclose error handling, size limits, redirects, whether robots.txt parsing is case-insensitive, or what 'group counts' precisely means. The description also gives no hint that unrelated parameters like json or zone might affect behavior.

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 is efficient and easy to parse, but it may be too terse given the mismatch between the stated purpose and the broader schema.

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 4 parameters, no required fields, no annotations, and no output schema, the description is insufficient. It does not explain how the parameters map to the robots.txt fetch, what 'group counts' actually counts, or whether the other parameters (json, zone) are used at all. Agents cannot reliably determine correct 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?

Schema coverage is 100%, but the parameter descriptions in the schema are misaligned with the tool's stated purpose: 'url' is described as 'HTTPS URL to normalize or cite', 'json' as 'JSON text to validate; discarded after the check', and 'zone' as 'IANA timezone name' — none of which relate to fetching robots.txt. The tool description adds no parameter-level clarification, so the agent receives conflicting or irrelevant semantics.

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 gives a specific verb ('Fetch'), a clear resource ('public robots.txt'), and a precise outcome ('return group counts only'). It also uses 'only' to signal a narrow scope. However, it does not differentiate itself from the sibling tools by name, and the input schema's parameters (json, zone) suggest additional behaviors not mentioned.

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 about when to use this tool versus the siblings (citation, normalize-url, validate-json, timezone). The only implied usage is 'when you need robots.txt group counts,' but the presence of json and zone parameters alongside siblings that handle those concerns makes the selection unclear.

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