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 only states that it returns group counts, but fails to mention that most of the 9 parameters are ignored or that the tool performs a shape check that discards many inputs. The schema hints at this ('discarded after the shape check') but the description does not, leaving significant behavioral ambiguity.

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, which is positive, but it lacks structure and essential details. Given the tool has 9 parameters and no output schema, the extreme brevity becomes a drawback rather than an asset, leaving out critical invocation information.

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 is highly complex with 9 parameters, no output schema, and no annotations. The description provides only the high-level purpose and none of the mechanics, making it completely inadequate for an agent to use correctly. It does not explain how to specify the robots.txt URL, what 'group counts' means, or what the response format 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?

Despite 100% schema coverage, the parameter descriptions are unrelated to fetching robots.txt (e.g., 'Git ref name', 'City name for a public weather hint'). The tool description does not map any parameter to the URL for robots.txt, so an agent cannot know how to invoke the tool correctly. The description adds no meaningful clarification beyond the schema, and the schema's descriptions conflict with the tool's stated purpose.

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: 'Fetch a public robots.txt and return group counts only.' This clearly names the resource and the result. However, it does not differentiate from sibling URL-related tools like 'fetch-status' or 'web-fetch', and does not indicate which parameter supplies the URL, so it is not fully unambiguous.

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 offers no guidance on when to use this tool versus alternatives, nor any exclusions or context. An agent cannot determine whether to pick this over 'fetch-status' or 'web-fetch' based on the description alone.

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