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

The description discloses the read-only fetch behavior and output shape at a high level, but does not mention error handling, redirects, parsing behavior, or whether network requests are made. With no annotations, this leaves important behavioral details unspecified.

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, direct sentence with no unnecessary words. It is well-structured and immediately understandable.

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 nine parameters, no output schema, and no explanation of which parameter identifies the robots.txt URL, the description is far from complete. An agent cannot reliably invoke this tool with the correct arguments based on the information provided.

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 parameter descriptions appear copied from unrelated schemas ('Git ref name', 'JSON text to validate', 'IANA timezone name') and do not map to fetching robots.txt. The tool description itself does not explain how any parameter is used, leaving the agent unable to select the correct argument.

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 clear action and output: fetch a public robots.txt and return group counts only. However, with nine unrelated parameters and no indication which parameter selects the target, the purpose is less actionable than it could be.

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 use this tool versus any sibling tool such as web-fetch, fetch-status, or normalize-url. No prerequisites, alternatives, or context for use are mentioned.

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