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

With no annotations, the description carries the burden of explaining behavior. It does disclose that this is a public network fetch and that only group counts are returned, implicitly read-only. However, it does not mention error handling, rate limits, valid URL form, or what happens for missing robots.txt files.

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?

A single, front-loaded sentence that uses every word efficiently. No filler, no repetition, and the 'group counts only' qualifier is clear and helpful.

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 nine optional parameters, no output schema, and no annotations, the description is too minimal. It does not state which parameter targets the robots.txt, does not clarify how the returned group counts are structured, and does not account for failure modes or edge cases.

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 covers all nine parameters with descriptions, so the baseline is 3 even without addtional param info in the description. However, the description does not map 'public robots.txt' to any of the parameters—there is no 'robots.txt URL' parameter and no indication that host, url, or path should be populated.

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 precisely names the resource (public robots.txt), the action (fetch), and the output (group counts only). This makes the tool easily distinguishable from sibling tools like web-fetch and fetch-status without needing to open their schemas.

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 about when to use this tool versus alternatives such as web-fetch, domain-shape, or browser-url-ok, and no conditions or exclusions are given. The agent is left to infer use cases from the tool name and description.

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