Scroll Element Into View

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

Annotations already indicate the tool is destructive (destructiveHint: true) and not idempotent, so the description's addition of 'before a later action' is useful context but not rich behavioral detail. It does not contradict annotations, and no additional side effects or failure modes are mentioned.

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 directly conveys the tool's purpose without redundancy. Every word earns its place, and it is front-loaded with the key verb 'Scroll'.

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, the existence of an output schema, and detailed input schema, the description is sufficient for basic understanding. It could include more on edge cases or failure behavior, but for a simple scroll action, the current description plus schema covers the essentials.

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?

The input schema describes the 'center' and 'selector' parameters, and schema coverage is 67% (2 of 3 parameters). The tool description adds no parameter-specific guidance, but the schema carries most of the load, leaving only 'timeout' underdocumented. This is adequate but not enhanced by the description.

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's function: 'Scroll an element into the viewport before a later action.' This uses a specific verb ('scroll'), resource ('element'), and scope ('into the viewport'), making it distinct from sibling tools like page_scroll or element_click.

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 phrase 'before a later action' provides clear context for when to use this tool: as a preparatory step before interacting with an element. It does not explicitly mention alternatives or exclusions, but the intended use case is evident.

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