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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says it fetches and returns group counts; it does not mention failure behavior, redirects, rate limits, authentication needs, or whether the URL must point directly at a robots.txt. This is minimal disclosure for a network-fetching tool.

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 is front-loaded with the main verb and resource. It is concise, though the conciseness comes at the cost of critical operational detail.

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 no annotations, no output schema, 9 parameters, and a one-line description. More importantly, there is a severe semantic mismatch between the tool's stated purpose and the parameter schema. An agent cannot determine the required input, expected output format, or edge cases from this description alone.

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 has 9 parameters, none required, and their descriptions are entirely disconnected from the tool's stated purpose. For example, 'url' is described as 'HTTPS URL to normalize or cite' rather than as the robots.txt URL to fetch, and other parameters ('city', 'zone', 'query') appear unrelated. The description does not clarify which parameter should be supplied to fetch the robots.txt, leaving an agent unable to select the correct argument.

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'), the resource ('a public robots.txt'), and the output shape ('return group counts only'). This is specific enough to distinguish it from generic web-fetching tools like web-fetch or fetch-status, though it does not explicitly name an alternative.

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 implies the tool should be used when someone needs group counts from a robots.txt file, but it gives no explicit guidance on when not to use it or which sibling tool to prefer. There are no stated exclusions or alternative-routing cues.

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