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

With no annotations, the description must carry the transparency burden. It does disclose that the operation fetches a public resource and that only group counts are returned, implying a read-only action. However, it omits behavior around invalid URLs, redirects, missing robots.txt files, or error handling.

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 filler or redundancy. It front-loads the key action and immediately specifies the narrow output, making it easy to scan and understand.

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?

Given the nine-parameter input schema and no output schema, the description is too sparse. It does not explain how parameters relate to the robots.txt fetch, what the group-count output looks like, or how failures are reported, leaving an agent without enough context for reliable 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?

The schema has descriptions for all nine parameters, so the baseline is 3 even though the tool description does not map parameters explicitly. The 'url' description is somewhat generic ('normalize or cite'), but the tool name and overall description make it plausible that 'url' is the intended robots.txt target.

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 exact output ('return group counts only'), which makes the tool's purpose immediately understandable. The robots.txt resource and counts-only result distinguish it from generic fetch or status tools.

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 does not explain when to choose this tool over alternatives such as web-fetch or fetch-status, nor does it mention any exclusions, prerequisites, or fallback conditions. It only states what the tool does, leaving the agent without decision guidance.

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