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

With no annotations, the description carries the transparency burden. It does disclose that only group counts are returned rather than full robots.txt contents, which is useful. However, it does not mention failure behavior for missing/inaccessible robots.txt files, redirect handling, or that many schema parameters appear to be discarded rather than used.

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 short sentence with no filler. It front-loads the action and resource, then states the output constraint. It earns its place despite being minimal.

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 9 optional parameters, no output schema, and no annotations, this one-sentence description is incomplete. It does not explain which parameters are actually used, what the returned group counts look like, how failures are reported, or how this tool relates to the many sibling shape/fetch tools.

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 generic and not tailored to this tool: 'url' is described as 'HTTPS URL to normalize or cite' and 'host' as 'Public hostname', with no indication which one drives the robots.txt fetch. The tool description adds no parameter mapping, leaving an agent to guess between url, host, or possibly another field.

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 is clear and specific: it names the verb ('Fetch'), the resource ('a public robots.txt'), and the output ('return group counts only'). It does not explicitly differentiate from siblings like web-fetch or fetch-status, but the 'group counts only' qualifier gives enough specificity to avoid confusion with a full-content fetch.

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 this tool versus alternatives such as web-fetch, fetch-status, or normalize-url. The description implies a simple use case but does not state prerequisites, exclusions, or when another sibling would be more appropriate.

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