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

The description implies a network fetch action but does not explicitly state read-only behavior, potential errors, or any side effects. With no annotations, it leaves key behavioral details unspecified.

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 concise sentence, but it omits essential information about parameter usage and expected behavior, making it structurally incomplete despite being brief.

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 lack of output schema, irrelevant parameters, and missing guidance on parameter mapping, the description is highly incomplete. An agent cannot correctly invoke this tool based on the provided information.

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 parameters bear no clear connection to the described action. Schema descriptions like 'Git ref name' or 'City name for a public weather hint' appear arbitrary and do not map to fetching robots.txt or counting groups. The description provides zero explanation of how parameters are used.

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 clear verb ('Fetch') and object ('public robots.txt') and mentions returning group counts, but the listed parameters (ref, city, zone, query, etc.) have no obvious relation to robots.txt, muddling the actual purpose. It does not effectively differentiate from sibling fetch tools.

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 on when to use this tool versus alternatives like fetch-status or web-fetch. The description provides no context for selecting this tool.

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