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

No annotations provided, so the description must carry the behavioral burden. It states 'Fetch' but the schema suggests a validation tool that discards most inputs. No disclosure of what happens to parameters, side effects, or actual behavior. The mismatch is a serious transparency failure.

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 one short sentence, which is concise, but it is so incomplete and misleading that it fails its purpose. Brevity does not compensate for incorrect content.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description provides almost no context. It does not explain the actual multi-purpose validation nature, what 'group counts' means, or how parameters relate to the stated action. Completely inadequate for an agent to use 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?

While schema coverage is 100%, the description adds no meaning to the parameters and actively misleads by implying a robots.txt fetch. It fails to clarify that parameters like city, feed, and json are for separate validation checks, not for fetching robots.txt.

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 claims to fetch a public robots.txt and return group counts, but the schema lists 9 unrelated parameters (city, feed, json, zone, query, etc.) with descriptions indicating they are validation checks. This is misleading; the purpose is unclear and contradicts the schema.

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 on when to use this tool versus siblings like fetch-status, browser-url-ok, or normalize-url. The description does not mention alternatives or exclusion criteria.

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