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. It states the action but doesn't describe what happens after navigation (e.g., page load, potential errors, timeouts), whether it waits for completion, or if it requires specific permissions. This leaves significant gaps for a browser navigation tool.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place without redundancy.

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 no annotations and no output schema, the description is incomplete for a browser navigation tool. It doesn't explain return values, error conditions, or behavioral traits like loading behavior. For a tool that interacts with a browser, more context is needed to use it effectively.

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 description coverage is 100%, so the schema already documents the single 'url' parameter. The description adds no additional meaning beyond what the schema provides (e.g., URL format requirements, validation rules). The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 ('Navigate Safari') and target resource ('to a specific URL'), making the purpose immediately understandable. It distinguishes from siblings like 'go_back' or 'go_forward' by specifying URL-based navigation rather than browser history. However, it doesn't explicitly contrast with all siblings (e.g., 'refresh_page' also navigates but to the same URL).

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. It doesn't mention when navigation is appropriate versus other browser actions like 'click_element' or 'execute_script', nor does it specify prerequisites (e.g., requires Safari to be open). The agent must infer usage from the name alone.

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