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 successfully discloses the implementation mechanism (screencapture + PDF rendering) and UI interaction mode (none needed), but omits critical file operation behaviors such as overwrite policies, error handling for invalid paths, or return value confirmation.

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 sentences with zero waste: the first establishes core purpose, the second provides essential implementation context. Every word earns its place and the description is appropriately front-loaded.

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 single-parameter tool without output schema, the description is nearly complete. It adequately covers the 'what' and 'how', though it could be improved by noting file overwrite behavior or return confirmation given that this performs a file system write operation.

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 description coverage is 100% for the single 'path' parameter, establishing a baseline of 3. The description does not mention the parameter, but since the schema fully documents it (including the example path format), no additional semantic clarification is required from the description.

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 (Save), target (current page), and output format (PDF). This effectively distinguishes it from sibling tools like safari_screenshot (image output) and safari_extract_images (extraction vs. saving).

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 PDF format specification implicitly guides selection versus image-based screenshot tools, but there is no explicit guidance on when to choose this over safari_screenshot, nor any warnings about file overwrites or prerequisites.

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