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

With no annotations provided, the description must disclose behavior. It only says it fetches and returns group counts, but does not mention which parameters are used, whether it performs network I/O, what constitutes 'group counts', or any side effects. This is minimal transparency beyond the name.

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, front-loaded with the core action. However, it is under-specified, so the conciseness is not effectively used to convey necessary detail.

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 the tool has 9 parameters, no output schema, and no annotations, the description is woefully incomplete. It fails to explain which parameters are relevant, what the return value looks like, or any constraints, making it insufficient for an agent to call the tool correctly.

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?

The description adds no information about parameters. The schema contains 9 parameters with descriptions, but they are unrelated to fetching robots.txt (e.g., city, ref, feed). The description does not clarify which parameter is the URL or host, leaving the agent unable to determine how to invoke the tool correctly.

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), resource (public robots.txt), and output (group counts only), which is clear and distinct from generic fetch tools. However, it does not explicitly differentiate from siblings like web-fetch or fetch-status, though the 'group counts only' qualifier adds uniqueness.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention any exclusions or context that would route an agent here instead of a sibling like web-fetch or normalize-url.

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