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

With no annotations, the description must disclose behavior. It claims to 'fetch' but does not explain what happens on failure, whether it is a shape check rather than a real fetch, or any side effects. The output 'group counts only' is ambiguous regarding format.

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 short sentence, which is concise, but it is under-specified rather than efficiently informative. It front-loads the purpose but omits essential usage and context, so it does not earn its place fully.

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 required fields, no output schema, and no annotations, the description is inadequate. It does not explain which parameter to use, what the return value looks like, or how it differs from other fetch/shape tools.

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 parameters are documented. However, the description does not indicate which of the 9 parameters is relevant (likely 'url' but not stated), nor does it add meaning beyond the schema. Baseline of 3 applies because schema covers all fields.

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'), resource ('robots.txt'), and outcome ('return group counts only'). This is clear enough to distinguish from sibling tools like web-fetch or fetch-status, though it does not explicitly name an alternative.

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 given on when to use this tool versus siblings like browser-url-ok, domain-shape, or web-fetch. It does not state prerequisites (e.g., URL must be public) or when not to use it.

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