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

With no annotations, the description carries the full burden. It mentions fetching a public resource and returning group counts, but it does not disclose network behavior, error handling, whether parameters are ignored, or side effects. The schema parameter descriptions also imply unrelated behaviors (e.g., discarded values, no disk access), creating confusion.

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, front-loaded sentence with no filler. It is concise, though perhaps too terse given the confusing parameter list.

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 nine optional parameters with mismatched descriptions and no output schema, the description is far from complete. It does not explain how to construct a valid call, which parameters are relevant, what 'group counts' refers to, or what the returned data looks like.

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?

Although the schema has descriptions for all parameters, they are not semantically aligned with fetching robots.txt. Terms like 'Git ref name', 'weather hint', 'RSS or Atom URL', and 'IANA timezone name' appear unrelated, and no parameter is explicitly identified as the robots.txt location. The tool description adds no parameter-level clarity.

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, it does not indicate which of the many optional parameters supplies the robots.txt URL or host, making it hard to disambiguate from sibling tools like web-fetch or fetch-status.

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?

No guidance is provided about when to use this tool versus alternatives such as web-fetch, fetch-status, or normalize-url. There is no mention of prerequisites, fallback behavior, or explicit conditions that favor this tool.

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