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

Annotations are absent, so the description carries the full burden. It discloses one behavioral trait — output is reduced to group counts rather than full content — but says nothing about 404 handling, redirect behavior, auth expectations for 'public' access, or the unusual fact that most parameters are 'discarded' as the schema hints.

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 brief and front-loaded with the core action, but it is terse to the point of under-specification for a tool with nine parameters. The missing parameter mapping and behavioral details mean the sentence does not fully earn its place.

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 output schema, and no annotations, an agent cannot determine which parameter selects the robots.txt source, what the response shape is, or how failures are reported. The description is seriously incomplete for a tool with this much surface area.

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 coverage is 100%, but the parameter descriptions are borrowed from unrelated domains (city weather hint, feed, JSON validation, git ref) and no parameter is described as the robots.txt input. Only url or host plausibly apply, so an agent cannot determine which parameter specifies the target. The description fails to bridge the tool's purpose to its 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 clear verb+resource: fetch a public robots.txt, and adds a scope constraint ('return group counts only') that distinguishes it from a full-content fetch like web-fetch. It does not name sibling alternatives, but the core action and output restriction are unambiguous.

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 siblings such as web-fetch, fetch-status, browser-url-ok, or playwright-url-ok, all of which can fetch a URL. No when/when-not conditions, prerequisites, or alternative routing are mentioned.

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