滚动到页面元素

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does disclose the key behaviors: finding by CSS selector, using scrollIntoView, centering in the visible area, and returning position info. It omits potential side effects or return structure details, but for a scroll tool the disclosed behavior is reasonably transparent.

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?

One dense, front-loaded sentence conveys the action method, targeting mechanism, and return value without any wasted words. Every clause contributes useful information.

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?

The tool is simple, has one required parameter, and a fully documented schema. The description covers the core operation and return value, but since there is no output schema, the vague 'position info' could be more precise about what the returned data actually contains.

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 description coverage is 100%, so the baseline is 3 and the description need not repeat parameter details. The description adds no real parameter-level meaning beyond the schema; mentioning the CSS selector simply restates what the schema already says.

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 states a specific action (scroll to center via scrollIntoView), a specific resource (element found by CSS selector), and a concrete output (post-scroll position info). This clearly distinguishes it from sibling tools like click, hover, or get_screenshot.

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 explains how the tool operates but gives no guidance on when to use it versus alternatives or when not to use it. An agent gets no explicit context about conditions that should trigger scroll_to instead of eval_js or other navigation-related approaches.

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