Safari MCP Server

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

No annotations are provided, so the description carries the full burden. It adequately describes the destructive nature of the operation but lacks details about scope (domain-specificity), error behavior when keys don't exist, or reversibility that would help an agent understand edge cases.

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 that front-loads the primary action ('Delete a localStorage key') and immediately qualifies the alternative behavior. There is no extraneous information; every clause serves to clarify the tool's dual functionality.

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 (one optional parameter) and complete schema coverage, the description is sufficient for correct invocation. No output schema exists, so return value explanation isn't expected. Minor gap regarding storage scope/permissions, but adequate for the tool's complexity level.

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 schema already fully documents the parameter behavior ('Key to delete (omit to clear ALL)'). The description mirrors this information effectively but does not add significant semantic meaning beyond what the schema already provides, meeting the baseline expectation for high-coverage schemas.

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 (Delete) and resource (localStorage), including the dual behavior of single-key deletion vs. clearing all. It effectively distinguishes from siblings like safari_delete_cookies and safari_delete_session_storage by specifying the storage type.

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 explicit guidance on how to trigger the 'clear all' behavior by omitting the key parameter. While it doesn't explicitly compare when to use this versus sessionStorage deletion or other storage tools, the parameter-level guidance is clear and actionable.

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