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

With no annotations, the description carries the full burden of behavioral disclosure, but it fails to mention that most parameters are ignored (as indicated in the schema, e.g., 'discarded after the shape check'). It also does not disclose network access, potential failures, or the meaning of 'group counts.' The description is vague about side effects and operational details, leaving the agent without critical behavioral context.

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, clear sentence with no unnecessary words, making it concise and front-loaded. It effectively communicates the core action and output, though it could be slightly longer to address other dimensions without losing efficiency.

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 has 9 parameters, many unrelated to the stated purpose, and no output schema, yet the description only provides a minimal summary of the return value ('group counts only'). It does not explain what 'group counts' means, how parameters affect the fetch, or what the full response structure looks like. For a tool with this complexity, the description is inadequate for correct invocation.

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 the baseline is 3. The description adds no information about parameters beyond what the schema already states, and several schema descriptions are misleading (e.g., 'city' is for a weather hint, unrelated to robots.txt). The tool description does not clarify which parameters are actually relevant to fetching robots.txt, so it fails to add value beyond the schema.

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 output ('return group counts only'), giving a specific verb and resource. However, it does not differentiate from sibling tools like 'web-fetch' or 'fetch-status', which also handle URL fetching, so it lacks sibling distinction.

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, nor any exclusions or context about the tool's specific niche. An agent would have to infer when 'inspect-robots' is appropriate from the name alone, which is not reliable given the many similar tools.

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