Safari MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not specify whether scrolling is smooth or instant, what happens when scrolling exceeds page boundaries, whether it operates on the viewport or full document, or what the return value indicates.

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 efficient sentence of nine words that front-loads the action. While appropriately concise for a simple two-parameter tool, it may be overly minimal given the lack of sibling differentiation and behavioral context that would require additional sentences.

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 presence of similar sibling tools (scroll_to, scroll_to_element) and lack of output schema or annotations, the description is incomplete. It omits critical context about relative vs. absolute scrolling behavior and does not indicate what distinguishes this from other scrolling options in the tool suite.

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 100% schema description coverage, the schema already fully documents both parameters including defaults (direction default: down, amount default: 500). The description maps 'up or down' to direction and 'amount' to pixels but does not add validation constraints, units clarification, or usage examples beyond what the schema provides.

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 specific action (Scroll) and scope (the page up or down by a specified amount). However, it fails to distinguish from siblings 'safari_scroll_to' and 'safari_scroll_to_element', which likely perform absolute scrolling or element-targeted scrolling rather than relative directional scrolling.

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 no guidance on when to use this tool versus alternatives, particularly the similar 'safari_scroll_to' and 'safari_scroll_to_element' tools. It does not mention prerequisites such as requiring an active page or when scrolling is preferable to other navigation methods.

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