compare_sets

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

The description discloses the threshold-based meaning of 'identical: true' and states that previews of most-changed pages are returned. With no annotations provided, the description carries the burden for behavioral disclosure, but it does not mention side effects, authentication requirements, or resource implications.

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 three short, focused sentences with no filler. The core purpose is front-loaded, and each sentence adds distinct, useful information.

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?

For a 6-parameter tool with no output schema and no annotations, the description is not complete enough for reliable invocation. The semantics of several parameters and the exact output format remain undocumented, leaving meaningful gaps for an agent.

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 by explaining parameters. It provides some meaning for before/after (labels or directories) and threshold (used in the identical condition), but align, max_images, and max_changed_ratio are left unexplained, making it difficult to configure calls beyond defaults.

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 uses a specific verb ('Diff') and resource ('two capture sets'), and clarifies that the sets can be labels from capture_set or directories. It distinguishes the tool from image-level comparison tools at a general level, though it does not explicitly name sibling alternatives.

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 intended use case is implied: compare capture sets and identify page-level differences. However, there is no explicit guidance about when to use this tool versus siblings like compare_images or ab_compare, nor any stated exclusions.

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