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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Fetch' and 'return group counts only'; it does not disclose timeouts, handling of missing or invalid robots.txt files, caching, redirects, or whether the full response is discarded. The minimal safety profile (read-only public fetch) is implied but not explained.

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 filler. Every word contributes to the core message, and the action and output constraint are stated directly.

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 required fields, no annotations, no output schema, and many siblings, the description is far too sparse. It does not explain what 'group counts' means, what output shape to expect, which parameter is the fetch source, or how errors surface, so an agent cannot reliably invoke it correctly.

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%, none of the parameter descriptions mention robots.txt or explain how to point the tool at the target site. The description adds no parameter mapping, leaving the agent to choose among url, host, path, and ref without evidence. This is a significant gap for a tool with nine optional 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 states a specific action ('Fetch a public robots.txt') and a specific result ('return group counts only'), making the tool's core purpose immediately clear. It also distinguishes itself from sibling fetching/checking tools by focusing on robots.txt rather than general web content or URL shape validation.

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 choose inspect-robots over web-fetch, domain-shape, or other siblings. The description implies use when robots.txt group counts are needed, but it does not state exclusions, prerequisites, or which parameter supplies the target site, so an agent must guess the invocation context.

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