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. It adds behavioral context through the example (selecting words in text) but omits execution details like synchronization behavior, error handling when elements aren't found, or whether coordinates are viewport-relative or absolute.

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?

Single sentence structure front-loads the action verb, efficiently combines targeting options with the 'or' conjunction, and appends a parenthetical example that adds value without verbosity. No redundant or wasted phrases.

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's straightforward purpose (3 simple parameters, no output schema), the description provides sufficient context for invocation. It could be improved by clarifying whether selector and coordinates are mutually exclusive or if one takes precedence when both are provided.

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?

While schema coverage is 100% (baseline 3), the description adds valuable semantic context by framing the parameters as alternatives ('CSS selector or x/y coordinates'), clarifying that these represent two different targeting approaches rather than complementary filters.

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?

Description clearly states the specific action (double-click), target resource (element), and targeting mechanisms (CSS selector or x/y coordinates). The name 'safari_double_click' distinguishes it from siblings 'safari_click' and 'safari_right_click', and the description reinforces this specific interaction pattern.

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?

Provides an example use case '(e.g. to select a word in text)' which implies when to use the tool, but lacks explicit guidance on when to prefer coordinates vs. selectors or when to use this versus the single-click 'safari_click' sibling.

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