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. It successfully communicates the blocking nature of the operation ('waits for page to fully load'), but omits other critical behavioral details such as timeout handling, error behavior on failed loads, or tab context assumptions.

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 consists of two efficient sentences with zero waste. The primary action ('Navigate to a URL in Safari') is front-loaded, followed immediately by the critical behavioral qualifier ('Waits for page to fully load').

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 single-parameter navigation tool without an output schema, the description adequately covers the essential function and blocking behavior. It could be improved by mentioning error handling or load failure scenarios, but it is sufficiently complete for the tool's complexity level.

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 the single 'url' parameter. The description reinforces this with 'Navigate to a URL' but does not add additional semantic context such as URL format requirements, protocol handling, or validation rules beyond what the schema already provides.

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 tool navigates to a URL in Safari and specifies it waits for the page to fully load. However, it does not explicitly differentiate from sibling tools like 'safari_navigate_and_read' or clarify when simple navigation is preferred over navigation with reading.

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?

There is no explicit guidance on when to use this tool versus alternatives such as 'safari_navigate_and_read', 'safari_reload', or history navigation. While 'waits for page to fully load' implies synchronous behavior, it does not constitute clear usage guidelines or prerequisites.

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