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

With no annotations, the description carries the full burden. It states the tool fetches and returns counts, but it does not disclose error handling, network behavior, or that the tool likely ignores most of its 9 parameters. The parameter descriptions repeatedly mention 'discarded after the shape check,' which contradicts the stated purpose of fetching robots.txt, leaving the actual behavior unclear.

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, concise sentence that front-loads the primary action and output. It is appropriately sized, though it omits critical information about parameter usage, which prevents a higher score.

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 is complex with 9 parameters and no output schema or annotations. The description is far too brief to explain how the parameters relate to the robots.txt fetch, which parameter to provide, or what 'group counts' means. An agent cannot confidently invoke the tool correctly based on this definition 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?

Schema coverage is 100%, so baseline is 3, but the description does not add any parameter-specific meaning. The parameter descriptions are generic (e.g., 'City name for a public weather hint') and unrelated to robots.txt, making it impossible to know which parameter actually drives the fetch. The tool description does not clarify the role of the url or any other parameter, so the schema's descriptions are not helpful for this tool's purpose.

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) and resource (public robots.txt) with an explicit outcome (return group counts only). It is clear and distinguishes itself from sibling shape-check tools by indicating a network fetch. However, the input schema contains many unrelated parameters (city, zone, query, path, etc.) that are not mentioned in the description, creating ambiguity about which parameter is actually used, which slightly reduces clarity.

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 provides no guidance on when to use this tool versus alternatives like web-fetch or fetch-status. It does not mention prerequisites, exclusions, or context in which the tool is appropriate. An agent has no basis to decide between this and sibling fetch/check tools.

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