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

With no annotations, the description carries the behavioral burden. It usefully discloses that the operation is a read-only public fetch and that output is deliberately limited to group counts. However, it does not address error behavior, redirects, whether the target is derived from host or url, or any rate/limit expectations.

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 with no filler. Every word contributes either the operation, the target, or the output limitation.

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?

Despite 9 optional parameters, no annotations, and no output schema, the description provides only one sentence. It does not say which parameters to supply, how unrelated parameters should be ignored, what a group count looks like, or what happens when the fetch fails. This is insufficient for reliable invocation.

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, but the description adds no parameter-level meaning. None of the parameter descriptions mention robots.txt, and the description does not clarify whether host, url, or path is the intended input, leaving the mapping to the agent to infer.

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 uses a specific verb ('fetch'), a concrete resource ('a public robots.txt'), and an explicit output shape ('return group counts only'). This clearly distinguishes inspect-robots from siblings like web-fetch or fetch-status, which target general URLs or statuses.

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?

The text establishes a clear context: use this when the task is to fetch a public robots.txt and needs only group counts, not full content. It stops short of explicitly naming sibling alternatives or stating when to prefer web-fetch over this tool, so it misses the top score.

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