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

Annotations already declare readOnlyHint=false and openWorldHint=true. The description adds no additional behavioral context beyond stating the action. It does not disclose side effects (e.g., no scroll limits, behavior when selector is invalid).

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, well-structured sentence with front-loaded context '[Playwright Browser]'. Every word earns its place; no waste.

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?

For a simple scroll tool, the description is minimally adequate. It mentions scrolling page or element, direction, and amount. However, it lacks details on return values, behavior when element not found, and edge cases.

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 only loosely explains parameters: 'amount' is in pixels, 'direction' is implied, 'selector' is optional. It fails to enumerate possible direction values or clarify that direction defaults to 'down'.

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 verb 'Scroll' and the resource 'page (or an element)', with explicit parameters for direction and amount. It distinguishes itself from all sibling tools as the only scroll action.

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 when to use (scrolling) but provides no explicit guidance on when not to use, prerequisites, or alternatives. The context is clear by naming but lacks exclusions.

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