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 reveals a network read operation and an output limit, but doesn't disclose what happens when robots.txt is missing, whether content is cached, network/rate considerations, or how 'group counts' are derived. For a network-facing tool this is a significant gap.

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?

A single, front-loaded sentence with zero filler. It states the action, target, and output constraint in ten words. Every word earns its place.

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?

For a tool with four optional parameters, no output schema, and no annotations, one sentence is insufficient. It doesn't explain the meaning of 'group counts', how the four seemingly unrelated parameters (url, host, json, zone) relate to the operation, or any behavioral details like error handling. A network tool needs considerably more context.

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 the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides, but it also doesn't need to given full coverage. The relevance of 'json' and 'zone' to fetching robots.txt remains unclear, though that's a schema-design issue rather than a description failure.

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 precise output scope ('return group counts only'). This distinguishes the tool's core function clearly, though it does not explicitly differentiate it from sibling 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?

The description implies a use case (retrieve robots.txt group counts) but provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The qualifier 'public' hints at scope but doesn't explain constraints like URL format or failure handling.

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