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. It successfully discloses the performance characteristic (saves a round-trip) and atomicity, but lacks disclosure of side effects (browser history mutation), error handling behavior, or the specific format of the returned 'page content' (HTML, text, etc.).

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?

Two tightly constructed sentences with zero redundancy. Front-loaded with the core action, followed immediately by the benefit and usage instruction. Every word earns its place.

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?

Adequate for a 3-parameter tool with full schema coverage, but lacks return value specification needed due to missing output schema. The phrase 'return the page content' confirms output existence but omits format details (markdown, HTML, text) that would complete the behavioral picture.

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% (all 3 parameters documented), establishing a baseline of 3. The description does not add additional semantic context beyond the schema (e.g., URL format restrictions, truncation behavior when maxLength is exceeded).

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?

Explicitly states the dual action ('Navigate to a URL and return the page content') and the atomic nature ('in one step'). Clearly distinguishes from siblings by contrasting with 'navigate+read_page' and naming the specific alternative tools to avoid.

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?

Provides explicit when-to-use guidance ('Use instead of safari_navigate + safari_read_page') and explains the efficiency benefit ('saves 1 full round-trip'), giving the agent a clear decision criterion for selecting this over the separate navigation tools.

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