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 explains the action naming convention (removing 'safari_' prefix, with examples like 'readPage' suggesting camelCase conversion). However, it fails to disclose execution semantics: whether steps are atomic/transactional, what happens if a step fails mid-sequence, or the structure of return values (no output schema exists).

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?

Extremely efficient at two sentences. The first sentence front-loads the core benefit (batching in one call), and the second immediately explains the data structure and naming convention. Zero redundant words.

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 the complexity of a batching tool with dynamic action dispatch and the absence of both annotations and output schema, the description is minimally adequate. It covers input construction well but omits critical runtime behavior (error handling, return format, step isolation) that an agent needs to safely orchestrate multi-step operations.

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?

Although schema coverage is 100%, the description adds crucial semantic context not present in the schema: the specific examples ('navigate', 'click', 'fill', 'evaluate', 'readPage') and the explicit rule that these correspond to sibling tool names sans prefix. This helps the agent correctly populate the 'action' strings.

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 batches 'multiple Safari actions in ONE call', using a specific verb (batch) and distinguishing it from the 60+ individual safari_* sibling tools. It immediately conveys the consolidation value proposition.

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?

It implies the primary use case (batching multiple actions vs individual calls) and provides the critical mapping rule that actions correspond to sibling tool names without the 'safari_' prefix. However, it lacks explicit guidance on when not to use it (e.g., for single actions) or error handling differences from individual tools.

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