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

With no annotations provided, the description carries the full burden of explaining side effects. It only says 'fetch,' implying a network read, but it does not disclose error behavior, caching, or whether any data is retained; the parameter descriptions further muddy this by referencing discarded values and unrelated checks.

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 main description is a single concise sentence, but the tool definition is padded with nine optional parameters whose descriptions appear copied from other tools. This clutter makes the overall structure poor and detracts from the clear one-line purpose.

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 description lacks an output schema, error semantics, and an explanation of how the optional parameters map to the robots.txt request. It is not complete enough for an agent to reliably construct a correct call.

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's parameter descriptions are largely irrelevant to fetching a robots.txt file: 'ref' is a Git ref, 'city' is a weather hint, 'json' is to validate, and 'query' is search text. The 'url' and 'host' descriptions are generic and do not explain how they relate to the robots.txt target, so the schema is actively misleading.

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 a specific action (fetch) and resource (public robots.txt) with a defined output (group counts only), which distinguishes it from generic fetching or validation tools. However, it does not specify which input parameter identifies the target robots.txt or what 'group counts' means in detail.

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 indication of when to prefer this tool over siblings such as web-fetch, fetch-status, or normalize-url. There is no mention of use cases, prerequisites, or exclusions.

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