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

Since no annotations are provided, the description bears the full burden. It implies a read-only network fetch and notes the output is only group counts, but it does not explain which parameters are actually used to locate the robots.txt, nor what happens on errors, unreachable hosts, or rate limits. The behavioral disclosure is minimal.

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 efficient sentence that front-loads the action and limits the output scope. There is no wasted wording or redundant 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?

With 9 non-required parameters, no annotations, and no output schema, the description is too sparse. It does not say how the agent should select the correct parameter for the robots.txt URL, what 'group counts' actually means, or what a typical response looks like. This leaves significant gaps for correct invocation.

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 all 9 parameters are individually described in the schema. The tool description adds no extra parameter context, such as which parameter is the required URL or host for the robots fetch. Per the baseline rule, this is a 3.

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 'Fetch a public robots.txt and return group counts only' states a specific verb (Fetch), a specific resource (public robots.txt), and a specific output (group counts only). This clearly distinguishes it from generic fetch tools like web-fetch or fetch-status.

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 explicit guidance on when to use this tool versus alternatives such as web-fetch or fetch-status, and does not mention when it is appropriate or inappropriate to invoke. It only states what it does, leaving the decision entirely to the agent.

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