Safari MCP Server

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

Provides scope context ('current page') which is valuable behavioral information. 'Delete' clearly signals destructive operation. However, lacks disclosure of side effects (e.g., potential logout), reversibility, or what happens when both name and all are provided or when neither is provided.

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?

Single sentence with zero waste. Front-loaded with action verb, covers both operational modes (specific/all) and scope (current page) efficiently.

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?

Sufficient for a 2-parameter tool with full schema coverage and no output schema, but gaps remain regarding parameter interaction rules (optional fields) and destructive side effects that should be addressed given the absence of 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?

Schema coverage is 100%, establishing baseline 3. Description adds the 'or' relationship between specific/all modes, but does not clarify parameter precedence, mutual exclusivity constraints, or provide examples for the optional parameters.

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?

Specific verb 'Delete' with clear resource 'cookies' and scope 'current page'. Distinct from siblings like safari_get_cookies (get vs delete), safari_set_cookie (set vs delete), and safari_delete_local_storage (cookies vs 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?

Implies two modes (specific cookie vs all) but provides no explicit when-to-use guidance, no mention of using safari_get_cookies first to identify targets, and no explanation of parameter interaction logic (both params are optional with required=0).

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