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

There are no annotations on this tool, so the description carries the full behavioral disclosure burden. It says the fetch is public and that only group counts are returned, but it does not disclose what happens with inaccessible or non-public URLs, whether values are ignored, or how failures or malformed robots.txt files are handled.

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 compact sentence with no filler. It front-loads the action and the output restriction, making it easy to read and immediately actionable.

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?

The tool has nine optional parameters, no output schema, and no annotations, yet the description only gives a high-level purpose. It does not clarify which parameter supplies the robots.txt URL or what shape the returned group counts take, so an agent would struggle to invoke it confidently from the description alone.

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?

Since the schema has 100% parameter description coverage, the baseline is 3. The description does not add meaning beyond the schema; it also does not say which of the nine parameters is the robots.txt URL or how the unrelated-looking optional parameters such as city, zone, and json relate to the tool's behavior.

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 verb and resource: fetch a public robots.txt and return only group counts. This is distinct from every sibling tool listed, none of which is about robots.txt or group counts, so an agent can clearly tell what this tool does.

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 description provides no guidance on when to use this tool instead of alternatives like web-fetch or normalize-url, and it states no exclusions or when-not-to-use conditions. The only usage signal is implied from the resource name and the verb.

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