cdp_scroll

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions the three modes but does not state side effects, return values, or behavior when conflicting parameters (e.g., selector and x/y) are provided together.

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 with no redundancy, efficiently communicating all three scrolling capabilities.

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 6 parameters, three modes, no output schema, and no annotations, the description is too sparse. It lacks parameter combination rules, return value, and edge-case behavior, which are essential for correct autonomous invocation.

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 descriptions only cover x/y and session_id (50% coverage). The description adds meaning by linking selector to element scroll and delta_x/delta_y to wheel scrolling, but it doesn't clarify parameter relationships, defaults, or precedence among modes.

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's purpose with a specific verb ('scroll') and enumerates three distinct modes: element scroll, wheel delta, and coordinate jump. This distinguishes it from sibling tools.

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 provides clear context on when to use the tool: for scrolling by element, delta, or coordinates. It doesn't explicitly mention alternatives, but the scenarios themselves guide selection.

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