Fuzz Compare

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

The description goes beyond the annotations by explaining the read-only nature, the GET requests through the rate limiter, the clustering by body hash, and the cache-poisoning probe behavior. It discloses exactly what happens (diffing dimensions, re-fetch) and the safety constraints, aligning with readOnlyHint and destructiveHint. No contradictions.

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 well-structured: it opens with the core purpose, then explains parameters, then details the optional re_request and safety. Each sentence carries information, no filler. It is appropriately sized for a tool with this complexity.

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 tool's complexity (fuzzing, diffing, cache poisoning) and the presence of an output schema, the description covers all essential operational details: what is diffed, how clustering works, the cache-poisoning probe, and safety. Nothing an agent needs to invoke it correctly is missing.

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 0%, so the description must compensate. It does: it explains baseline_url as the unmodified request, case_urls as the injected variants, and re_request as a second fetch for cache poisoning. Every parameter is meaningfully described, adding value beyond the bare schema.

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 verb (diff) and resource (responses against a baseline), clearly distinguishing it from sibling tools like authz_compare or web_injection_probe. It also names the exact inputs (baseline_url, case_urls) and the outcome (find what a payload changed).

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 explains the purpose and how to use the tool (provide baseline and case URLs), and clarifies the re_request option. It does not explicitly mention alternatives or when not to use it, but the context is clear enough that an agent can infer its niche. A bit more explicit routing would earn a 5.

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