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

With no annotations, the description carries the full burden, but it only discloses that the fetch is 'public' and returns 'group counts only.' It omits request behavior, error handling, and the fact that the schema contains unrelated parameters like json and zone.

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 front-loaded sentence with no filler. However, it is terse to the point of omitting essential contextual information, so it is not maximally effective.

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?

No output schema exists, yet the description never defines what 'group counts' means or what the return shape looks like. It also leaves the 4-parameter schema unexplained in the context of robots.txt, making it difficult for an agent to invoke correctly.

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 the schema nominally covers all parameters, the descriptions are mismatched: url references 'normalize or cite,' json is 'to validate,' and zone is a timezone parameter—none clearly tied to fetching robots.txt. The tool description does not explain which parameter to use, so the schema fails to provide usable semantics for this tool.

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 a public robots.txt') and the result ('return group counts only'). This specific resource and output restriction distinguish it from generic fetch tools, though it does not explicitly compare it to siblings.

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?

No guidance is given about when to use this tool versus alternatives or when not to use it. The word 'only' hints that full robots.txt content is not returned, but no exclusions or alternative tool names are mentioned.

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