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 offers minimal information. It does not indicate whether the operation waits for page load completion, affects browser state beyond the cache bypass option, or has any side effects on console/network logs.

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 extremely concise at three words, with no redundancy. However, given the lack of annotations and behavioral context, it is arguably too minimal—bordering on under-specification rather than efficient front-loading of critical information.

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 tool without output schema, the description provides the minimum viable context to identify the tool's function. However, it lacks important browser automation context (e.g., load state behavior, timing) that would be necessary for reliable agent operation.

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 'hard' parameter ('Hard reload (bypass cache)'). The description does not mention this parameter, but per scoring guidelines, with schema coverage >80%, the baseline score is 3 even without additional parameter semantics in the description text.

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 ('Reload') and target ('the current page'), providing specific verb and resource identification. However, it does not explicitly differentiate from sibling navigation tools like 'safari_navigate' or 'safari_go_back', relying on the agent to infer the distinction between reloading and navigating.

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., when to hard reload vs. regular reload, or when to use navigate instead). There are no prerequisites, exclusions, or conditional usage hints provided.

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