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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns 'group counts only' and fetches a public robots.txt, which implies network access and read-only behavior. However, it does not disclose error handling, timeout behavior, or how unrelated parameters (e.g., city, feed, zone) are treated. The description is too sparse for a tool with no annotation safety profile.

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 sentence, front-loaded with the core action and result. There is zero fluff, and it efficiently conveys the primary function.

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 tool has 9 parameters, no output schema, and no annotations, yet the description is extremely minimal. It does not explain what 'group counts' means, how the parameters relate to the primary function, or why many seemingly unrelated parameters exist (e.g., city, feed, json). The description is inadequate for an agent to correctly invoke this tool without further schema inspection, and even then the purpose of the extra parameters remains unclear.

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?

Schema description coverage is 100%, so each parameter is already documented. The description adds no parameter semantics beyond what the schema provides; it does not clarify which parameter is the target for robots.txt (likely 'url') nor explain the role of the other eight parameters. Baseline 3 is appropriate because the schema covers the parameters, but the description offers no extra value.

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') and resource ('public robots.txt') with a defined result ('group counts only'). It is clear but does not explicitly differentiate from sibling tools like web-fetch or fetch-status that also fetch URLs. A 4 reflects clarity without sibling distinction.

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 alternatives. It does not mention exclusions, prerequisites, or scenarios where another tool (e.g., web-fetch) would be more appropriate. The only implied usage is 'if you need robots.txt group counts', but this is not explicit.

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