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 discloses the significant behavioral trait that omitting the key clears all storage, which warns of a destructive bulk operation. However, it omits scope details (tab-specific, session-bound) and does not explicitly characterize the deletion as irreversible.

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 a single, efficient sentence of 12 words. It is front-loaded with the action ('Delete') and immediately qualifies the scope, with zero wasted verbiage.

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 low complexity (one optional parameter, simple binary behavior), the description adequately covers the essential operational contract. While annotations are absent, the combination of the clear description and complete schema documentation provides sufficient context for 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 input schema has 100% description coverage, establishing a baseline of 3. The description restates the schema's explanation of the 'key' parameter ('omit to clear all') without adding additional semantic context such as key format constraints or examples.

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 a specific verb ('Delete') with a specific resource ('sessionStorage'), clearly distinguishing it from siblings like safari_delete_local_storage and safari_delete_cookies. It also specifies the dual mode (single key vs. clear all).

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 description provides implicit usage guidance by explaining how to trigger 'clear all' behavior (omitting the key), but it lacks explicit guidance on when to use this tool versus alternatives like safari_set_session_storage or safari_session_storage (read).

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