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

With no annotations, the description must carry behavioral disclosure. It states only that it 'return[s] group counts only,' which hints at output shape, but it does not clarify how the parameters affect behavior or whether it performs network calls, error handling, or discards inputs. The mismatch between description and schema leaves critical behavior opaque.

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 with no wasted words. However, conciseness is not the same as completeness; the extreme brevity omits essential information about parameter usage and the tool's actual scope, making it under-specified rather than efficiently concise.

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 required parameters, no output schema, and no annotations, the description is woefully incomplete. It fails to explain which parameter triggers robots.txt fetching, what the output looks like beyond 'group counts,' or how to handle the unrelated parameters. An agent cannot reliably invoke this tool, making it effectively unusable without external knowledge.

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% coverage with per-parameter descriptions, those descriptions are unrelated to the tool's stated purpose. For example, 'url' is described as 'HTTPS URL to normalize or cite,' not as a target for fetching robots.txt. The description adds no parameter meaning, and the schema does not compensate; an agent cannot deduce which parameter (if any) supplies the robots.txt URL. This is a severe gap.

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 resource, but the input schema presents nine unrelated parameters (city, feed, json, path, etc.) that do not align with robots.txt. This creates ambiguity about what the tool actually does—it either performs many unrelated checks or the schema is misaligned. The purpose is clear in isolation but misleading in context, so it only partially clarifies intent.

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 gives a single-line use case (fetch robots.txt) but no guidance on when to choose this over siblings like 'fetch-status', 'web-fetch', or 'domain-shape'. There is no mention of exclusions or alternatives, so an agent cannot determine when this tool is appropriate versus others.

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