scroll_and_record

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

With no annotations, the description carries the full burden but only mentions the high-level actions. It does not disclose potential side effects such as triggering scroll events that might affect page behavior, nor does it explain what happens to the recorded video or screenshots. This lack of behavioral detail is a significant gap for a tool that manipulates page state.

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 avoids redundancy and gets straight to the point. It earns its place with no filler words.

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?

Despite having four parameters and no output schema or annotations, the description only provides a high-level summary. It omits information about the scrolling process (stepped, speed), the output artifacts (video file, screenshots), and any potential pitfalls, making it insufficient for reliable tool selection.

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 50% (stepDelay and scrollSpeed have descriptions). The description adds no parameter semantics, leaving recordVideo and captureScreenshots to rely on their names. The tool fails to explain how these booleans relate to the capturing behavior.

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 the entire page while recording video and capturing scroll-triggered animations. This is a specific verb+resource combination that distinguishes it from siblings like get_scroll_triggers or capture_current_state.

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 usage for full-page scroll capture but provides no explicit when-to-use or alternatives. An agent must infer from context that this is for recording animations during scrolling, but there's no guidance on when to prefer this over get_scroll_triggers or watch_element.

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