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

No annotations are provided, so the description carries the full transparency burden. It discloses that the tool fetches a public robots.txt and only returns group counts, implying other data is discarded. However, it does not clarify what happens to the 9 input parameters (most of which are marked 'discarded' in the schema), nor does it explain side effects, rate limits, or error behavior. The schema hints at discarding but the description adds minimal behavioral context beyond the stated output.

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 only one sentence and is appropriately brief. The main action is front-loaded ('Fetch a public robots.txt'). However, it earns little of its place because it omits critical linkage to the schema and usage context. It is concise but underspecified, making it less useful than a longer description that explains parameter roles.

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?

Given the tool's complexity (9 parameters, no required fields) and the absence of annotations and output schema, the description is severely incomplete. It does not explain how to invoke the tool correctly, what the parameters do in relation to the described purpose, or what 'group counts' means. An agent would be unable to call this tool with confidence. The description is far less than the minimum needed for such a complex tool.

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 input schema provides descriptions for all 9 parameters (100% coverage), so the baseline should be 3. However, the description fails to connect these parameters to the tool's stated purpose (fetching robots.txt). For instance, it never indicates which parameter supplies the robots.txt URL. The description adds no value beyond the schema and actually contradicts the impression that all fields are relevant. This misalignment reduces the score below baseline.

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 states a clear verb and resource ('Fetch a public robots.txt') and a specific output ('group counts only'). However, the parameter schema contains 9 unrelated optional fields (ref, city, feed, json, zone, query, etc.) that are not mentioned or mapped in the description. An agent reading the description alone would not know which parameter(s) correspond to the robots.txt URL or how the other fields factor in, creating confusion about the tool's actual scope.

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 its siblings (e.g., fetch-status, web-fetch, normalize-url). It does not mention alternatives, exclusions, or prerequisite conditions. The agent is left to guess whether this tool is suitable for a given use case.

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