Scroll

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain side effects, precedence among x/y/selector/scrollIntoView, or whether scrolling is instant or smooth. This is a significant transparency gap for a tool with no 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 one sentence, concise, and front-loaded with the verb. It avoids unnecessary words, though it sacrifices essential detail. It is appropriately sized for a simple scroll action but under-specified for the schema.

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?

With 5 parameters, 0% schema coverage, no annotations, and no output schema, the description must compensate heavily. It does not explain parameter semantics, return values, or usage context. This is far below the minimum viable for a tool with this complexity.

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 0%, and the description does not mention any parameter. The phrase 'page or element' vaguely maps to x/y for page and selector for element, but scrollIntoView and sessionId are entirely unexplained. The agent cannot infer how to set the parameters correctly.

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 a page or element into view, using a specific verb and resource. It distinguishes this from navigation and clicking, though it does not explicitly reference sibling tools. The ambiguity about what 'page' means (top/bottom, coordinates) is minor.

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?

No guidance is given on when to use this tool versus alternatives like click or navigate. It does not mention prerequisites (e.g., session), scenarios (e.g., after locating an element), or exclusions. The agent is left without context for invoking this tool correctly.

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