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

With no annotations, the description carries the full burden, but it is misleading. The parameter descriptions indicate 'discarded after the shape check' and similar, suggesting a generic shape-validation tool, yet the description claims a robots.txt fetch. This internal contradiction means the agent cannot predict actual behavior. No side effects, permissions, or response details are disclosed.

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, making it very concise and front-loaded. However, it is so under-specified that the conciseness is a detriment; there is no wasted text, but it omits essential context. Still, the length itself is appropriate for the minimal content.

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 drastically incomplete. It fails to explain how the parameters are used, what the 'group counts' mean, or what inputs are expected. An agent would be unable to call this tool correctly based on the description alone.

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%, so each parameter has a description, but the overall description adds no meaning and actively misleads. It does not explain how these parameters relate to fetching robots.txt, and the parameter descriptions themselves (e.g., 'discarded after the shape check') contradict the tool's stated purpose. The description fails to compensate for the schema's disconnected parameter set.

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 clear action and resource ('Fetch a public robots.txt and return group counts only'), but it directly conflicts with the parameter set, which includes city, feed, json, zone, etc., none of which relate to robots.txt. It fails to distinguish from siblings like fetch-status or web-fetch, and the stated purpose is misleading.

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 any sibling. No mention of prerequisites, use cases, or alternatives. The description gives no context about when a robots.txt fetch would be appropriate or how it differs from similar tools.

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