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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose that the tool performs a network fetch of a public resource and returns only counts rather than full content. However, it does not explain what 'group counts' means, how missing or malformed robots.txt responses are handled, or that several schema parameters appear to be 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 one short sentence with no filler, and the main action is front-loaded. It loses a point because the extreme brevity omits needed routing information, but as a concise statement it is well structured.

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 optional parameters, no output schema, and no annotations, this definition is incomplete. It does not say which parameter supplies the target URL, what the returned counts look like, or how this tool differs from the large sibling set of fetch and shape tools.

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 schema description coverage is 100%, the tool description adds no parameter mapping: it never identifies which of ref, url, city, feed, host, json, or path should receive the robots.txt URL. The schema descriptions themselves are generic and unrelated to robots.txt (e.g., 'normalize or cite', 'weather hint', 'validate'), leaving the agent unable to invoke the tool confidently.

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 names a specific action ('Fetch'), a concrete resource ('a public robots.txt'), and an output constraint ('return group counts only'). This distinguishes it from most siblings, which deal with URLs, keys, or fetch status. However, it leaves 'group counts' undefined and does not map the purpose to any of the 9 schema parameters.

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?

There is no explicit guidance about when to use this tool versus the many related siblings such as web-fetch, fetch-status, normalize-url, or domain-shape. The only usage signal is implied by the action itself, with no exclusions, alternatives, or preconditions stated.

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