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

With no annotations, the description carries the full burden for behavior. It states that only group counts are returned and that the target is public, but it omits the return format, error behavior, missing robots.txt handling, redirects, or whether the full file is internally fetched.

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 sentence that front-loads the main action and output. It is concise and contains no filler.

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?

For a tool with no output schema and no annotations, the description is too sparse. It does not explain the input parameters, the shape of the returned group counts, error cases, or operational details such as redirects or robot exclusion, leaving important context missing.

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 contains four parameters, but the descriptions are largely unrelated to fetching robots.txt: url is described as 'HTTPS URL to normalize or cite', json is for validation, and zone is a timezone. Only host is plausibly relevant, and the description does not explain how any parameter is used.

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), the resource (public robots.txt), and the output (group counts only). It is specific enough to distinguish from the sibling tools, though it does not specify how the target URL or host is supplied.

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 guidance on when to use this tool versus alternatives, and no mention of when it is appropriate or inappropriate. The phrase 'group counts only' implies a reduced-output use case, but no explicit alternative is named.

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