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

With no annotations, the description carries the full burden. It states it fetches and returns group counts but does not disclose any side effects, network behavior, or whether it is read-only. It also does not explain how the various parameters are used, leaving behavior opaque.

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 concise, but the schema is bloated with 9 parameters, most of which have no obvious connection to the tool's stated purpose. The overall structure is confusing and could have been simplified to just a URL parameter.

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 description lacks essential context: it does not explain what 'group counts' means, what the output format is, or how the parameters (if any) should be used. There is no output schema, so the agent has insufficient information to confidently invoke this tool.

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 9 parameters with descriptions, but these descriptions are irrelevant to robots.txt. For example, 'ref' is 'Git ref name; discarded after the shape check' and 'city' is 'City name for a public weather hint; discarded after the call'. These descriptions are misleading and do not clarify how any parameter relates to fetching a robots.txt file. They appear to be generic placeholders.

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 clearly states a specific action and resource: 'Fetch a public robots.txt and return group counts only.' This distinguishes it from general fetch tools like web-fetch.

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 over alternatives such as web-fetch or fetch-status. It does not mention scenarios where group counts are needed.

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