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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait—returning 'group counts only' rather than full content—and implies a read-only fetch of a public resource. However, it does not mention error behavior, redirects, rate limits, or the fact that most parameters are discarded after the call.

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 single sentence is tight and front-loads the core purpose plus the key output restriction. It earns its place, though it is arguably too compressed given the complexity of the nine-parameter schema.

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?

There is no output schema and no annotations, so the description must explain the full invocation picture. It does not say which parameter holds the robots.txt URL, what the returned group counts look like, or how this tool behaves differently from sibling network inspection tools, making it incomplete for correct call construction.

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 description coverage is 100%, so the baseline is 3; the description does not need to re-list parameter meanings. However, the description introduces 'robots.txt' without mapping it to any of the nine parameters, leaving an agent unable to determine whether url, host, or something else is the actual target.

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 identifies a specific action ('Fetch'), a specific resource ('public robots.txt'), and a specific output ('group counts only'). It is clear at a surface level, but it does not distinguish this tool from siblings like web-fetch, fetch-status, or browser-url-ok, and it does not state which input parameter supplies the robots.txt URL.

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 inspect-robots versus any of the many sibling fetch/shape/status tools. The description says what the tool does but gives no contextual trigger, prerequisite, or exclusion condition.

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