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

With no annotations at all, the description carries the full burden. It discloses that the tool performs a network fetch and only returns a counts summary, which is meaningful. However, it omits behavioral traits like error handling, missing robots.txt behavior, redirects, and rate limits.

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 appropriately brief and front-loaded, making the core behavior immediately clear. It loses a point because it is so terse that it skips the crucial input mapping to the tool's parameters.

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 has 10 optional parameters, no required parameters, no annotations, and no output schema, so the description is not complete enough to guide correct invocation. The description leaves an agent guessing which URL field to provide and what 'group counts' structurally represent.

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%, which sets the baseline at 3, but the description adds no parameter-level guidance. Given 10 optional parameters with several marked as 'discarded,' the description does not indicate which parameter(s) actually drive the robots.txt inspection, though the schema descriptions partly compensate.

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?

States a specific action ('Fetch a public robots.txt') and an exact output ('return group counts only'). This clearly identifies the resource being inspected and narrows the purpose enough to distinguish it from sibling fetch/shape tools.

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 gives no guidance on when to use this tool versus alternatives such as web-fetch, normalize-url, or domain-shape. The word 'public' hints at a precondition, but there are no explicit context cues, exclusions, or alternative tools mentioned.

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