Safari MCP Server

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

Without annotations, the description carries the full burden of behavioral disclosure. It successfully identifies which storage mechanisms are affected ('restores cookies, localStorage, sessionStorage'), but fails to specify whether this operation merges with or replaces existing data, or if it requires specific preconditions.

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, efficiently structured sentence that front-loads the core action ('Import storage state from JSON') and uses an em-dash to append specific behavioral details without redundancy. Every word earns its place.

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 single-parameter simplicity and lack of output schema, the description adequately covers the essential context: the source of the JSON, the specific storage types restored, and the relationship to the export sibling. It lacks only safety/destructiveness warnings that would be valuable for a state-mutation tool with no annotations.

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?

With 100% schema description coverage, the baseline is 3. The description mentions the JSON format and links to safari_export_storage, which aligns with the parameter description, but adds no additional syntax details, examples, or format constraints beyond what the schema already provides.

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 clearly states the specific action ('Import storage state from JSON'), identifies the exact data resources affected ('cookies, localStorage, sessionStorage'), and explicitly distinguishes itself from sibling tools by referencing 'safari_export_storage' as the source format.

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 establishes a clear workflow relationship with sibling tool 'safari_export_storage', guiding users to pair these tools for export/import cycles. While it implies bulk restoration versus individual edits, it does not explicitly mention granular alternatives like safari_set_cookie or warn against using this for single-value updates.

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