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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool fetches a public robots.txt and returns group counts, but does not disclose that many parameters (ref, city, json, query, etc.) are effectively ignored or discarded, as hinted in the schema. It also does not clarify error behavior, redirects, or what 'group counts' means. This is a significant gap for a tool with 9 parameters and no other metadata.

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 sentence, which is concise, but it is under-specified. It lacks front-loading of key usage details, such as which parameter identifies the robots.txt URL. The brevity is not effective because it omits essential operational context; it reads more like a stub than a guidance note.

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 output schema, and no annotations, yet the description is just one sentence. It does not explain which parameter drives the robots.txt fetch, what 'group counts' means, or how the other parameters are used (or ignored). For a tool with this complexity, the description is inadequate for an agent to call it correctly without additional context.

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?

Schema description coverage is 100%, so each parameter has an individual description in the schema. The tool description adds no extra meaning about how parameters relate to the tool's purpose—for instance, it does not specify that 'url' or 'host' is the primary input for the robots.txt fetch. Baseline 3 applies because the schema is complete, but the description fails to clarify parameter roles, leaving the mapping ambiguous.

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 specific verb ('Fetch'), a clear resource ('a public robots.txt'), and the output scope ('return group counts only'). This makes the tool's core function evident. However, it does not differentiate from sibling tools like web-fetch or fetch-status, which also fetch URLs, though the robots.txt specificity is a distinguishing factor.

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 gives no guidance on when to use this tool versus alternatives such as web-fetch, fetch-status, or normalize-url. There is no mention of prerequisites, edge cases, or when the tool is preferred. The agent is left to infer usage from the name and description alone.

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