compare_visual_regression

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does convey that the tool captures and compares screenshots, but it omits important behavior: whether an existing baseline is required, whether screenshots get persisted, whether the tool is read-only, or what the comparison returns. This is a significant transparency gap for an agent planning a call.

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 sentence with no waste. The verb, resource, and purpose are all front-loaded, and every clause contributes necessary 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?

With no output schema, no annotations, and closely related sibling tools, this description is incomplete. It does not explain the return format, how a baseline is established, whether a missing baseline produces an error, or how the tool's result relates to tolerancePercent. An agent cannot fully anticipate the tool's behavior or response.

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 schema already documents all three parameters. The description adds only marginal context by framing the tool around 'visual screenshots of a node or artboard' and implying tolerancePercent controls regression sensitivity, but it does not meaningfully extend the schema. Baseline 3 is appropriate.

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 ('captures and compares visual screenshots') with a target resource ('node or artboard') and an explicit outcome ('detect unexpected visual regression or layout drift'). However, it does not explicitly distinguish this tool from closely related siblings like get_screenshot or diff_design_nodes, leaving the baseline/comparison semantics largely implied.

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 stated purpose, 'detect unexpected visual regression or layout drift,' provides an implied use case, telling an agent when this tool might be helpful. But it gives no explicit guidance on when to choose this tool over alternatives, no exclusions, and no mention of prerequisites such as an existing baseline screenshot or comparison target.

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