Safari MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the hover action but fails to explain behavioral traits such as whether it triggers mouseover events, reveals tooltips, waits for animations, or what occurs if the element is not found.

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 extremely concise with zero waste—two short sentences front-loaded with the action verb. Every word earns its place; there is no fluff or redundant information.

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 100% schema coverage and lack of output schema, the description provides minimal viable information by covering the targeting mechanism. However, for a UI interaction tool with no annotations, it omits expected behavioral context such as event triggering or failure modes.

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?

Despite 100% schema description coverage, the description adds crucial semantic value by clarifying the relationship between parameters: 'Use ref, selector, or x/y' indicates these are alternative targeting methods rather than cumulative requirements, which the schema alone does not convey.

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 action ('Hover over element') with a specific verb and resource. However, it does not explicitly differentiate this tool from sibling click variants (safari_click, safari_double_click, safari_right_click), though the verb distinction is implicit.

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 phrase 'Use ref, selector, or x/y' provides basic syntax guidance for the targeting parameters, implying alternative methods. However, it lacks contextual guidance on when to use hover versus click, or prerequisites like requiring a page navigation first.

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