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

The description discloses the core behavior (network read of a public robots.txt) and that only group counts are returned. With no annotations, it does not cover error handling or side effects, but for a simple read-only fetch this is minimally transparent.

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; 'group counts only' is an efficient scoping constraint. Every word earns 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 no output schema or annotations, and nine optional parameters, the description does not tell an agent how to specify the robots.txt location or what exactly a group count is. The unrelated-looking optional parameters (city, feed, json, path) make the invocation path unclear, so the definition is not complete enough for reliable calling.

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 even though the description adds no parameter-level detail. The description never maps the robots.txt target to a schema parameter (url, host, or path), which is a notable gap.

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 verb and resource: fetch a public robots.txt, and narrows the output to 'group counts only.' This is distinct from generic web-fetch or fetch-status, though it does not explicitly contrast with any sibling.

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 choose inspect-robots over alternatives such as web-fetch, fetch-status, or normalize-url, and no exclusionary conditions. The agent must infer use from the tool name alone.

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