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

No annotations are provided, so the description carries the full disclosure burden. It indicates a read-only fetch and a limited return value, but says nothing about network failures, missing robots.txt, redirects, rate limits, authentication, or side effects.

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 front-loaded sentence with no wasted words, stating the action and output scope. It is appropriately concise as prose, though it is very terse for a 9-parameter tool.

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?

With 9 optional parameters, no annotations, and no output schema, a one-sentence description is not enough. It fails to identify which inputs are needed, what 'group counts' means, or how edge cases are handled, so an agent cannot reliably invoke the 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 schema coverage is 100%, the parameter descriptions are largely unrelated to robots.txt (city, feed, json, zone, query, etc.) and the description never maps any parameter to the robots.txt URL or host. High schema coverage is undermined by the mismatch between the tool purpose and the actual parameters.

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 names a concrete verb ('Fetch'), a specific resource ('a public robots.txt'), and an explicit output ('return group counts only'), so an agent can tell what the tool does. It does not explicitly distinguish itself from sibling fetch/URL tools, so it stops short of a 5.

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 on when to use inspect-robots instead of web-fetch, fetch-status, domain-shape, or other siblings, and no exclusions or prerequisites are given. The phrasing only implies a robots.txt use case without providing any routing context.

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