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

No side effects, permissions, rate limits, or error behavior are disclosed. With no annotations, the description carries full burden but remains silent on all behavioral aspects.

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, well-formed sentence with no wasted words. It is appropriately sized for the core functionality.

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?

The core function is stated, but the tool has 9 parameters and the description does not explain which are relevant or how they relate to the operation. There is no output schema, leaving the expected result shape unclear.

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 all 9 parameters have descriptions, they are generic and misaligned with the tool's purpose (e.g., 'url' described as 'HTTPS URL to normalize or cite'). They do not clarify how each parameter is used for fetching robots.txt, thus adding confusion rather than meaning.

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 specific action (fetch), the resource (public robots.txt), and the output (group counts only). It is concise and unambiguous.

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 provided on when to use this tool versus alternatives. The description does not compare with sibling tools or indicate specific scenarios for use.

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