scroll_and_snapshot

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic action (scroll then snapshot) and does not mention parameters like direction, amount, or waitMs that affect behavior. The schema provides details, but the description lacks contextual behavioral traits.

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 sentence that conveys the core purpose and use case without unnecessary words. It is highly concise and efficient.

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 tool has 4 parameters, no annotations, and no output schema, the description is insufficient. It does not explain parameter usage, behavior on scroll direction, or what happens after snapshot. The tool combines two actions but lacks completeness for an AI agent to use correctly.

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?

The input schema has 100% coverage for 4 parameters. The description adds no additional meaning or context to the parameters (e.g., what 'tabId' refers to, or how 'amount' is used). Baseline 3 is appropriate since schema covers the parameter semantics.

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 'Scroll the page and take a snapshot' and specifies the use case 'revealing content below the fold.' It distinguishes itself from sibling tools like 'scroll' (only scrolls) and 'snapshot' (only snapshot), making the purpose unambiguous.

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 includes 'Useful for revealing content below the fold,' which implies when to use the tool. However, it does not provide explicit when-not-to-use guidance or mention alternative tools like combining 'scroll' and 'snapshot' separately.

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