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

With no annotations, the description carries the burden of disclosing behavior. It states that only group counts are returned and implies a read-only network fetch, but it does not mention error cases, non-robots content, network requirements, or any side effects.

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 focused sentence with no filler. It conveys the essential purpose and output restriction efficiently.

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?

Without an output schema, annotations, or any indication of required versus optional parameters, the description is incomplete. The nine unrelated optional parameters and no mention of the output structure leave an agent unable to reliably invoke the 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?

Although all nine parameters have descriptions, they appear mismatched to the tool: 'ref' is a Git ref, 'city' is a weather hint, 'json' is validation text, and 'zone' is an IANA timezone. These descriptions do not clarify which parameter identifies the robots.txt and actively confuse the caller.

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 action and resource: fetch a public robots.txt file and return only group counts. It is distinguishable from generic tools like web-fetch and fetch-status, but the lack of any mention of which parameter supplies the URL leaves slight ambiguity.

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?

No guidance is given about when to use this tool instead of siblings such as web-fetch, fetch-status, or domain-shape. The phrase 'public robots.txt' implies a use case, but no explicit conditions, alternatives, or exclusions are provided.

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