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. It reveals that output is limited to group counts, but does not state that the operation is read-only, what happens on unavailable robots.txt files, whether requests are rate-limited, or any failure semantics.

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. Every word contributes to defining the core behavior and output scope.

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 four optional parameters, no annotations, and no output schema, yet the description explains only the high-level fetch behavior. It does not clarify which parameters are actually used, how to specify the target robots.txt, or what the returned group counts look like, leaving meaningful gaps 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 description coverage is 100%, so the baseline is 3. The description adds some context by linking 'robots.txt' to the URL/host parameters, but it does not clarify the relevance or irrelevance of the json and zone parameters, which appear unrelated to fetching robots.txt.

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 specific action ('Fetch'), a specific resource ('a public robots.txt'), and a specific output shape ('group counts only'). This clearly distinguishes inspect-robots from siblings like normalize-url, validate-json, and status-catalog.

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 implies use when robots.txt group counts are needed, but it gives no explicit when-to-use guidance, no exclusions, and does not compare against sibling tools. An agent is left to infer the appropriate context.

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