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

The description conveys that the tool performs a public network fetch and returns only group counts, which is useful context. However, with no annotations, the description still doesn't disclose failure behavior, robots.txt parsing specifics, rate limits, or what happens when the target is missing.

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 one tightly written sentence with no filler. It clearly front-loads the tool's behavior and output scope.

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 nine optional parameters, no annotations, and no output schema, this description is far too thin. It does not explain which parameters are relevant, how the robots.txt target is selected, what 'group counts' means exactly, or what the return value looks like.

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 the schema has 100% parameter description coverage, those descriptions are completely misaligned with the tool's stated purpose. Params like 'Git ref name', 'City name', and 'Search text' are described as discarded after unrelated checks, and no parameter is explicitly described as the robots.txt URL or host. An agent cannot determine which parameter to supply to fetch the intended 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 states a specific verb ('Fetch'), a specific resource ('a public robots.txt'), and a specific output ('return group counts only'). This gives a reasonably clear picture of what the tool does and somewhat distinguishes it from generic fetchers like web-fetch, but it doesn't clarify how the input parameters relate to this purpose.

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 implies the tool should be used when an agent needs robots.txt group counts, but it provides no explicit guidance about when to choose this over sibling tools like web-fetch or fetch-status. No alternatives or exclusions are mentioned.

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