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

No annotations are provided, so the description bears full responsibility for behavior. It fails to disclose how missing robots.txt, HTTP errors, redirects, or malformed content are handled, and it does not clarify that several parameters are ignored or discarded.

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 concise sentence, but it omits necessary parameter mapping and behavioral details. It is efficient in length but not optimally structured for usability.

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 nine optional parameters, no output schema, and no explanation of 'group counts', the description is contextually incomplete. An agent cannot infer the expected input format, return shape, or edge-case behavior.

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 parameter descriptions appear unrelated to robots.txt (e.g., city for weather, json for validation, query for length check). The main description does not explain how any of the nine parameters map to fetching a robots.txt, making the schema effectively useless for an agent.

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 ('public robots.txt') and specifies the output ('group counts only'), distinguishing it from generic web fetchers. However, it does not identify which parameter holds the robots.txt URL, limiting full purpose 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 instead of siblings like web-fetch, fetch-status, or normalize-url. The description does not mention selection criteria, prerequisites, or situations where the tool should be avoided.

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