vibeside_compare_visual_diff

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about side effects (e.g., that it may capture a live screenshot when 'current' is omitted), read-only safety, or what the comparison reports, leaving behavior largely opaque.

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?

A single front-loaded sentence with the alias note and the core action, zero filler. Appropriately sized for what it attempts to convey.

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?

With seven parameters and no output schema, the description should explain what the comparison returns (diff percentage, highlighted image, etc.) but says nothing. For a tool at this complexity level, it is under-specified.

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 all seven parameters are already documented in the schema (baseline, current, fullPage, selector, threshold, saveDiffPath, includeDiffImage). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Compare visual diff') and a clear scope (baseline screenshot/image vs current page or DOM element). It also flags itself as an alias for the sibling vibeside_visual_diff, which helps distinguish it, though it leaves the primary/alias preference ambiguous.

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?

Labels itself an alias but gives no guidance on when to use this tool versus vibeside_visual_diff itself, nor any preconditions (browser connected, baseline requirements). The agent must infer usage entirely.

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