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

The description mentions a network fetch and a limited return value, but lacks details about side effects, error behavior, rate limits, or whether any data is persisted. With no annotations provided, more behavioral disclosure is needed.

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 clear sentence with no fluff or redundant content. It is appropriately concise and front-loaded.

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?

With 9 optional parameters, no required fields, and no output schema, the description does not explain which parameters are actually used, what the return format is, or how to handle invalid inputs. The tool is effectively unusable based on the given information.

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% description coverage, the descriptions are mostly nonsensical and inconsistent with the tool's purpose. For example, 'url' is described as 'HTTPS URL to normalize or cite' rather than the robots.txt target, and many parameters are labeled as 'discarded' or irrelevant. This actively misleads rather than clarifies.

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 clearly states the tool fetches a public robots.txt and returns group counts, which is specific enough to differentiate it from general fetch tools. However, it does not explicitly name the input parameter that provides the target URL, slightly reducing clarity.

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 like web-fetch, fetch-status, or normalize-url. The description implies a robots.txt-specific use case, but does not state conditions or preferences.

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