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

With no annotations, the description carries the full burden of describing side effects. It says 'return group counts only' but does not explicitly state that the operation is read-only, whether it follows redirects, or what happens on fetch failure or missing robots.txt.

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 with no redundancy, front-loading the core action and result. While it is terse, it earns its place and is not padded, though it omits needed context that other dimensions capture.

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?

Given the complex, seemingly mismatched schema and no output schema or annotations, the description is far from complete. An agent cannot confidently determine which parameters to supply, what 'group counts' means, or what output format to expect.

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?

The schema contains nine optional parameters whose descriptions are generic and often unrelated to fetching robots.txt (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint'). The description does not explain which parameters are actually used or how they map to the tool's purpose, making invocation ambiguous.

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 clearly states a specific verb ('Fetch'), a resource ('public robots.txt'), and an outcome ('return group counts only'). It distinguishes the tool from web-fetch and fetch-status by focusing on robots.txt group counts, though it does not specify how the target URL is provided.

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 about when to use this tool versus sibling tools like web-fetch or normalize-url. The description mentions no prerequisites, no examples, and no conditions that would indicate appropriate usage.

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