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

With no annotations provided, the description carries the burden of explaining behavior, but it only says 'public' and 'return group counts'. It does not disclose network access, parsing rules, error handling, or side effects, though it is not contradictory.

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 sentence with no filler, and it front-loads the action and the key output qualifier ('only'). It is appropriately concise for the stated functionality.

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 the large 9-parameter schema, the absence of an output schema, and no annotations, the description is incomplete. It does not explain parameter roles, the return structure of group counts, or failure behavior, leaving significant gaps for an agent.

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?

The schema has 100% parameter description coverage, so the baseline is 3, but many parameter descriptions are unrelated to the stated robots.txt purpose (city, feed, json, zone, query) or say values are 'discarded'. The tool-level description adds no parameter context and leaves which inputs actually matter unclear.

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 concrete action ('Fetch a public robots.txt') and a specific output ('return group counts only'), which distinguishes it from generic web-fetching siblings. It does not clarify how the robots.txt location is derived from the parameters, but the core purpose is reasonably clear.

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 this tool over siblings like web-fetch, fetch-status, or browser-url-ok. It also omits prerequisites or the intended input for locating the robots.txt file.

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