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

With no annotations, the description bears the full burden of disclosing behavior. It fails to mention that the tool does not return the full robots.txt content, that it only operates on public URLs, or that the provided parameters may not actually affect the fetch. The mismatch between the description and the generic parameter names makes the tool's actual behavior opaque and potentially misleading.

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 superfluous words. It clearly and efficiently communicates the core action and result.

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 about how the tool determines which robots.txt to fetch, what constitutes a 'group', or how the provided parameters interact with the fetch. Given the generic and misleading parameters, the description is insufficient for an agent 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?

The schema includes parameters (url, host, json, zone) that are irrelevant to the described functionality of fetching a robots.txt and returning group counts. The description provides no mapping between these parameters and the tool's purpose, and the schema descriptions are generic placeholders unrelated to robots.txt.

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 ('Fetch'), a specific resource ('public robots.txt'), and a specific output ('return group counts only'). It is immediately obvious what the 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 versus any alternative. There is no mention of use cases, prerequisites, or conditions under which this tool is preferred.

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