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

The description discloses that the operation is a public network fetch and limits output to 'group counts only,' implying a read-only, summary-returning behavior. But with no annotations present, it does not cover failure behavior, 404/redirect handling, or what a 'group' means, leaving part of the behavioral burden uncovered.

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 tightly scoped sentence with a front-loaded verb and no filler. It communicates the operation and the output restriction in minimal space.

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 no annotations, no output schema, and a large list of unrelated optional parameters, the description does not tell an agent which parameter to supply or whether any input is required. It works as a purpose statement but is incomplete as a standalone invocation guide.

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 baseline is 3. The description adds the useful semantic clue that the target is a public robots.txt, which helps an agent lean toward the `url` parameter over `feed` or `host`, but it never names the parameter and the schema marks none required.

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 concrete resource ('a public robots.txt'), and an exact output ('return group counts only'). This distinguishes it from siblings like web-fetch or fetch-status by narrowing scope to robots.txt group counts, even though no sibling is named.

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 when to use the tool: when a public robots.txt's group counts are needed. However, it provides no explicit when-to-use versus when-not-to-use guidance and does not mention alternatives or exclusions, so the usage context is only inferred.

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