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

With no annotations, the description alone must disclose behavior. It claims a network fetch of robots.txt, but the schema parameters do not support this (e.g., 'url' is described as 'HTTPS URL to normalize or cite', not for robots). Side effects, error handling, and return format are unspecified. The behavior is opaque and inconsistent with the schema.

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 extremely brief, but brevity here sacrifices necessary detail. It lacks structure and does not clarify the intended parameter usage. While it is concise in word count, it is not appropriately sized for the complexity of the schema.

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 tool has 9 optional parameters, no annotations, and no output schema. The description does not explain how parameters map to the robots.txt fetch, what 'group counts' means, or how the tool behaves. An agent cannot successfully invoke this tool based on the available 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 every parameter has a description, they are generic and misaligned with the tool's stated purpose. For instance, 'host' and 'url' are vaguely defined, and none are clearly tied to fetching robots.txt. The descriptions do not help an agent understand which parameter to use or how. Semantics are effectively absent.

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 action (fetch) and resource (robots.txt) and output (group counts), but the parameter list is entirely generic and unrelated (ref, city, feed, etc.), creating confusion about what the tool actually does. The purpose is stated, but the mismatch undermines 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?

The description provides no guidance on when to use this tool versus alternatives. It neither mentions conditions for use nor distinguishes it from sibling tools like web-fetch or browser-url-ok. There is no usage context at all.

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