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

Annotations already declare destructiveHint=false and openWorldHint=true; the description reinforces non-destructiveness by stating it does not click or change values, which is genuinely additive. It does not disclose failure behavior (element not found, timeout), whether it waits for visibility, or why readOnlyHint is false for a scroll operation.

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?

Two short sentences, front-loaded with the action and immediately followed by the scope boundary. No filler or redundancy.

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 an output schema and full annotation coverage, the description only needs to carry intent and scope, which it does. The one residual gap is behavior on failure or non-visible targets, minor given the structured data available.

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%, so all nine parameters (device, endpoint, target_id, timeout_ms, title, url_contains, etc.) are already documented. The description only echoes selector/text targeting, adding no syntax or selection guidance beyond 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?

States a specific verb (scroll into view) and resource (a Chromium page element), plus the two targeting mechanisms (selector or visible text). It is distinguishable from browser_scroll in principle, but the description never names browser_scroll or ui_scroll_into_view, so the sibling boundary must be inferred.

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 second sentence provides a useful negative scope ('does not click the element or change its value'), which implicitly rules out browser_click and browser_set_value. However, there is no explicit guidance on when to choose this over browser_scroll, ui_scroll_into_view, or browser_find.

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