Scroll Page

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

Without annotations, the description carries the full burden of behavioral disclosure, but it only states the action and target. It does not mention whether scrolling is relative to the viewport, what happens if no tab is selected, or any side effects. The absence of safety or mutation details leaves the agent underinformed.

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, front-loaded sentence that is concise and to the point. However, it omits parameter details and usage context, making it less complete than ideal for a tool with four parameters.

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 four parameters, no annotations, and no output schema, the description is too minimal to be fully usable. It fails to explain coordinates, delta semantics, or the required context of a selected tab, leaving significant gaps for an AI agent.

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?

With 0% schema description coverage, the description must compensate by explaining the parameters, but it does not. The schema lists x, y, deltaX, and deltaY without descriptions, and the tool description only mentions 'mouse wheel event' without adding meaning to these fields.

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 dispatches a mouse wheel event in the selected tab, using a specific verb and resource. This distinguishes it from sibling tools like click and press_key, which target different input types.

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 implies the tool is for scrolling via mouse wheel events and requires a selected tab, but it does not explicitly state when to use it versus alternatives like click or press_key. No exclusions or alternative guidance is provided, leaving usage to be inferred.

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