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 claims to fetch robots.txt but omits that most parameters are discarded after validation (per schema descriptions), that network access is involved, or how group counts are derived. The actual multi-purpose behavior is hidden.

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, brief sentence, which is concise, but it under-specifies a tool with 9 parameters and a generic shape-checking role. Conciseness here sacrifices essential context, making it less useful than a slightly longer but accurate description.

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 high parameter count, no output schema, and no annotations, the description is grossly incomplete. It doesn't explain the 'group counts' result, how the tool handles the various inputs, or what distinguishes it from other shape checkers. The agent cannot reliably invoke it.

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 schema description coverage is 100%, the description adds no parameter-level meaning and even contradicts the schema by singling out robots.txt while most parameters (city, feed, json, path, zone, query) are unrelated. It fails to clarify which parameters apply to the stated purpose.

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 public robots.txt and return group counts only'), but the input schema exposes 9 unrelated parameters (city, feed, json, path, zone, query) that are described as shape-check candidates, not robots.txt inputs. This mismatch makes the tool's actual purpose unclear and fails to differentiate it from sibling shape-checkers like domain-shape or jira-key-shape.

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 given on when to use this tool versus alternatives. The description mentions only robots.txt, yet the schema implies a broader shape-checking role, leaving the agent without a clear selection rule. It neither states exclusions nor names sibling alternatives.

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