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 mention that sessionStorage is tab-scoped and cleared on session end, that setting overwrites existing keys, or any size constraints. 'Set' implies mutation but lacks safety/reversibility context.

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 efficient at 4 words with no filler. However, it may be overly minimal—bordering on under-specification—given the complexity of browser storage and the lack of annotations. One additional sentence on scope or persistence would improve utility.

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 annotations and no output schema, the description should disclose persistence characteristics and differentiate from localStorage. Given the presence of safari_set_local_storage and safari_set_cookie siblings, the description fails to help agents select the correct storage mechanism.

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 has 100% coverage with clear parameter descriptions ('Storage key', 'Value to store'). The description adds no specific parameter semantics beyond what the schema provides, meeting the baseline 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 verb (Set) and resource (sessionStorage), distinguishing it from siblings like safari_delete_session_storage or safari_session_storage (likely the getter). However, it lacks specificity about scope (e.g., 'for the current tab') that would make it a 5.

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_set_local_storage (persistence differences) or safari_session_storage (the getter). Given the rich ecosystem of 60+ sibling tools including storage variants, explicit differentiation is needed.

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