Safari MCP Server

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

With no annotations provided, the description carries full behavioral disclosure burden. It adds crucial information about automatically switching to the new tab (a side effect not in schema), but omits blocking behavior, return values, and timeout error handling.

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?

Two well-structured sentences with zero waste. The first establishes purpose and example; the second reveals critical behavioral trait (auto-switch). Information is front-loaded and appropriately dense.

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?

Adequate for a 2-parameter wait tool without output schema. The auto-switch behavior is documented, but the description could improve by mentioning what happens when timeout is exceeded (exception vs. null return) or what value is returned on success.

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?

Schema coverage is 100% with clear descriptions for both timeout (including default value) and urlContains. The description does not add parameter-specific semantics, but the baseline score of 3 is appropriate given the schema already fully documents both parameters.

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 uses specific verb 'Wait' with resource 'new tab' and provides a concrete example (OAuth login popup). It clearly distinguishes from siblings like safari_new_tab (creates vs. waits for creation) and safari_switch_tab (manual vs. automatic switching).

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 a clear contextual example ('after OAuth login click opens popup') that signals when to use the tool. However, it lacks explicit 'when not to use' guidance or named alternatives like safari_new_tab or safari_wait.

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