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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that the operation is a public read ('public robots.txt') and that output is intentionally limited ('group counts only'), but it does not describe failure behavior, rate limits, or whether the full robots.txt is ever returned.

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 no filler. It states the action, target, and output limit efficiently.

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 9 parameters, no required fields, no output schema, and a one-line description, the definition is not complete enough for an agent to invoke it confidently. It does not define 'group counts', specify which parameter to set, or describe the return shape.

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 schema has 9 optional parameters with 100% description coverage, but the descriptions are generic and geared toward many tools (e.g., 'HTTPS URL to normalize or cite', 'City name for a public weather hint'). The tool description never tells the agent which parameter supplies the robots.txt URL, so parameter selection remains ambiguous.

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 names a specific verb ('Fetch'), a concrete resource ('a public robots.txt'), and the exact output scope ('return group counts only'), which makes the tool's purpose unmistakable and distinguishes it from generic fetch tools like web-fetch or fetch-status.

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?

Usage is implied by the tool name and description: use it when you need robots.txt group counts. However, it does not state when not to use it or point to any alternative among the many sibling tools, so the guidance is minimal.

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