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

The word 'Fetch' and 'public' suggest a read-only network operation, and 'group counts only' limits the output. However, with no annotations provided, the description does not disclose error behavior, redirect handling, missing robots.txt handling, rate limits, or any other side effects beyond the minimal statement.

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 one tight sentence with no filler or redundant wording. It is concise, but it sacrifices necessary context about parameters and behavior.

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 9 optional parameters, no output schema, and no annotations, the description is far from complete. It does not explain which parameter supplies the target host/URL, what 'group counts' means exactly, or what the result shape looks like, so an agent cannot reliably call this tool.

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?

Although every parameter has a description, most descriptions are clearly unrelated placeholders or generic examples (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint', 'JSON text to validate; discarded after the check'). None of them coherently explain how the 9 optional parameters map to fetching and counting robots.txt groups.

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 action ('Fetch'), a clear resource ('a public robots.txt'), and a constrained output ('return group counts only'). This gives an agent a solid high-level understanding of the tool's core purpose.

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 provides no guidance on when to use this tool versus the many sibling tools like web-fetch, normalize-url, or domain-shape. There is no mention of preferred input, fallback behavior, or conditions that would make this tool the right choice.

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