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 states that only group counts are returned, but does not explain network behavior, failure modes, redirects, rate limits, or what 'group counts' actually means. For a network-fetching tool, this is a significant transparency gap.

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. It is concise and easy to scan, though it sacrifices critical parameter linkage.

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?

Given 9 optional parameters, no annotations, and no output schema, the description is too thin. It leaves the agent guessing about input selection, output shape, and edge cases, so it is not complete enough 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?

Although every parameter has a schema description, the tool description never connects robots.txt to any specific parameter. With 9 optional parameters including unrelated-looking ones like city, feed, and json, an agent cannot reliably determine which parameter supplies the robots.txt URL or host.

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 specific action ('fetch a public robots.txt') and a specific output ('return group counts only'), so the purpose is clear. It does not explicitly distinguish itself from siblings like web-fetch or fetch-status, 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 about when to use inspect-robots versus alternatives such as web-fetch, browser-url-ok, or normalize-url. The word 'only' hints at the tool's narrow scope, but no when-to-use or when-not-to-use context is provided.

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