browser_visual_component

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

With no annotations, the description carries full burden. It discloses auto-creation of baseline if missing, returning a baseline_created flag, and specifies return fields (diffPixels, diffRatio, passed). It could mention write operations explicitly, but overall transparent.

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 comprehensive sentence that efficiently conveys the tool's purpose, workflow, and return values. No wasted words; clear structure with arrow notation.

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 no output schema, the description explains return values sufficiently. It covers core functionality but could mention handling of existing baselines and potential side effects. Still complete enough 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 coverage is 100%, providing baseline of 3. The description adds workflow context (e.g., 'exactly select component' for selector) and clarifies the purpose of parameters within the comparison workflow, enhancing understanding beyond 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 clearly identifies the tool as performing component-level visual comparison, involving screenshot, baseline comparison, and return of diff metrics. It distinguishes from sibling tools like browser_visual_check (likely full-page) and browser_visual_snapshot (just snapshot).

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 implies usage for component-level baseline comparison but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria. The context of sibling tools helps, but the description lacks direct guidance.

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