scroll_element_into_view

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

Annotations already declare idempotentHint=true, indicating the call is safe to repeat. The description adds the crucial behavioral detail that scrolling uses the UIA ScrollItem pattern and operates on a container. This is valuable context beyond the annotations. It doesn't specify behavior when the element is already visible, but idempotency implies no-op.

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 two sentences with no wasted words. The first sentence delivers the core action and mechanism, the second provides usage context. Every sentence earns its place.

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?

For a single-parameter, idempotent scroll action with no output schema, the description is fully sufficient. It covers what the tool does, how it works, and when to use it. No critical information is missing.

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% with a clear description for elementId ('Element ID returned by find_element'). The tool description does not add any additional meaning about the parameter beyond what the schema already provides. 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?

The description clearly states the action ('Scroll a container'), the target ('given element'), the outcome ('becomes visible'), and the mechanism ('via the UIA ScrollItem pattern'). This distinguishes it from sibling tools like 'scroll' (generic scroll) or 'click_element' (which may require prior scrolling).

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 explicitly advises using the tool before clicking an element that may be outside the visible scroll area. This provides clear when-to-use guidance. While it doesn't list alternatives or when-not-to-use, the context is sufficiently clear for an agent.

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