Scroll Element Into View

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

Annotations already indicate destructive behavior (destructiveHint: true), so the description adds minimal context. It correctly states scrolling into viewport but does not discuss side effects like triggering scroll events or potential state changes. No contradiction with annotations.

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 concise sentence that front-loads the core action. No extraneous information 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?

Given the tool's simplicity and the presence of an output schema (not shown but declared), the description is adequate but lacks context on error handling (e.g., element not found, timeout behavior) and the return value. It does not explain prerequisites like element existence.

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 67% with descriptions for 'selector' and 'center' provided in the schema. The description adds no extra parameter meaning beyond the schema, so baseline 3 is appropriate. 'timeout' lacks a schema description but the description does not compensate.

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 states the tool scrolls an element into the viewport, which is a specific verb+resource action. However, it does not distinguish from the sibling 'page_scroll', which scrolls the entire page, though the element focus is 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 description provides no guidance on when to use this tool versus alternatives like 'page_scroll' or other element actions. The phrase 'before a later action' hints at chaining but does not explicitly exclude cases where scrolling is not needed.

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