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 but offers none. It does not state that this is a destructive write operation (overwrites existing keys), specify same-origin/domain constraints, or indicate that changes persist across sessions.

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?

Extremely concise at only four words with no redundancy. While efficiently structured, the brevity contributes to under-specification given the lack of annotations and behavioral context.

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 state-mutating tool with no safety annotations and no output schema, the description is inadequate. It omits persistence behavior, domain scoping, error conditions, and return value information necessary for safe invocation.

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?

The description does not reference the parameters (key, value) at all. However, the input schema has 100% description coverage ('Storage key', 'Value to store'), establishing the baseline score of 3 since the schema adequately documents the 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 states the basic action (Set) and target (localStorage), but fails to distinguish this tool from siblings like safari_set_session_storage or safari_set_cookie. It does not clarify that localStorage persists across browser sessions, which is crucial for correct tool selection.

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?

No guidance provided on when to use localStorage versus sessionStorage (sibling tool) or cookies. No mention of domain restrictions or prerequisites for successful storage.

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