Safari MCP Server

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

With no annotations provided, the description carries full burden but discloses minimal behavioral traits. It doesn't specify that this is a safe read-only operation, the return data format (object vs string), or error handling when keys don't exist.

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?

Six-word single sentence that immediately identifies the operation and target. No filler content; appropriately sized for a simple accessor tool.

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 simplicity and excellent schema coverage, the description is minimally adequate. However, lacking an output schema, it omits the return value structure and doesn't address the 'omit for all' behavior described in the schema parameter.

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% ('Specific key to get (omit for all)'), so the baseline is 3. The description adds no additional parameter context beyond what the schema already documents.

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 verb ('Get') and resource ('localStorage data') with scope ('current page'). It inherently distinguishes from siblings like safari_session_storage and safari_cookies by specifying 'localStorage', though it doesn't clarify differences from safari_export_storage.

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 this versus safari_export_storage (which likely persists to file) or safari_set_local_storage. No mention of prerequisites like page context requirements.

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