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

With no annotations present, the description carries the full burden for behavioral disclosure, but it only says 'fetch' without noting network access, potential latency, failure modes, or whether the operation is strictly read-only. It does not describe side effects or limitations.

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 tool description is concise and front-loaded, using a single sentence to convey the main action and output. The schema descriptions are also brief, but their brevity comes at the cost of correctness.

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?

Despite having no output schema, the description does not clarify what 'group counts' means or how parameters like url and host relate to fetching robots.txt. The mismatched parameter descriptions leave the agent without enough context to invoke the tool correctly.

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 covers 100% of parameters, the descriptions are clearly mismatched copy-paste text: 'url' says 'normalize or cite', 'json' says 'validate', and 'zone' says 'IANA timezone name'. These descriptions do not add relevant meaning for inspecting robots.txt and actively mislead an agent.

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 ('Fetch a public robots.txt') and a clear output ('return group counts'), which distinguishes it from sibling tools. It is slightly vague about what 'group counts' refers to, but the core purpose is understandable.

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 normalize-url or citation. There is no mention of prerequisites, typical use cases, or conditions that would make this tool preferable.

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