scroll_into_view

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

Discloses that it does not click, which is a key behavior. However, with no annotations, it lacks details like whether it waits for rendering, error handling for missing elements, or if it adjusts scroll behavior. Adequate but not comprehensive.

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 sentences, front-loaded with primary action and purpose. No redundant or unnecessary information. Highly efficient.

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 lack of output schema, the description adequately covers purpose, use, and key behavioral distinction. Could mention return value or failure behavior for completeness, but not essential.

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 has 100% coverage; description paraphrases schema parameter ('CSS selector of element to scroll to') without adding new meaning. Meets baseline but adds no extra value for parameter understanding.

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?

Description clearly states verb ('scroll'), resource ('element'), and adds 'without clicking it', distinguishing it from click_element. It also provides a specific use case (lazy-loaded content, scrolling to section).

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?

Description indicates when to use (lazy-loaded content, scrolling to section) but does not explicitly state when not to use or mention alternative tools. However, context is clear.

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