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 of behavioral disclosure but only specifies the scope ('current page'). It fails to disclose whether setting overwrites existing cookies, persistence behavior, security implications, or side effects on subsequent network requests.

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 single sentence 'Set a cookie on the current page' is maximally concise with zero redundancy. Every word serves a purpose, placing the action verb first and following with scope.

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 rich input schema (100% coverage) and lack of output schema, the description is minimally adequate. However, for a state-modifying operation with 7 parameters and no annotations, it should provide more behavioral context regarding persistence and page state requirements.

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 for all 7 parameters (name, value, domain, path, expires, secure, sameSite). The description adds no parameter-specific guidance beyond what the schema already 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 uses a specific verb ('Set') with clear resource ('cookie') and scope ('current page'). While it distinguishes from siblings like safari_get_cookies and safari_delete_cookies through verb choice, it does not explicitly articulate these differences or edge cases within the description text.

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 no guidance on when to use this tool versus alternatives (e.g., safari_delete_cookies for removal, or when to use domain/path filtering). It omits prerequisites such as requiring an active page navigation first or how to handle cookie conflicts.

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