MCP Safari Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'refresh' implies a page reload action, it doesn't specify whether this causes data loss on forms, triggers page re-authentication, or affects ongoing operations. No rate limits, side effects, or performance implications are mentioned.

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 perfectly concise at just 5 words, front-loading the essential action and target without any wasted words. Every element ('refresh', 'current', 'Safari', 'page') earns its place in communicating the core 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 zero parameters, no annotations, and no output schema, the description provides the minimum viable information about what the tool does. However, for a browser interaction tool that could have side effects (form data loss, re-authentication prompts), more behavioral context would be helpful despite the simple parameter structure.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing non-existent parameters, earning a baseline 4 for parameter semantics in this zero-parameter context.

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 action ('refresh') and target ('current Safari page'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'navigate' or 'go_back' which also affect page navigation, leaving room for improvement in sibling distinction.

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 like 'navigate' (for loading new URLs) or 'go_back/forward' (for browser history navigation). It lacks explicit context about when this refresh operation is appropriate versus other page manipulation tools.

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