Safari MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether this triggers input/change events, how it handles missing selectors, whether it clears existing values first, or what it returns—critical details for a browser automation 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?

At five words, the description is maximally concise with zero redundancy. Every word earns its place: 'Fill' (action), 'multiple' (scope/differentiator), 'form fields' (target), 'at once' (batch nature).

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 simple input schema (single array parameter) and lack of output schema or annotations, the description provides the minimum viable context for an agent to understand the tool's intent. However, it lacks behavioral specifics expected for a browser automation action.

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?

With 100% schema description coverage, the structured fields already document the 'selector' and 'value' pairs. The description adds minimal semantic value beyond the schema, merely confirming the batch nature ('at once'), which warrants the baseline score.

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 uses a specific verb ('Fill') and resource ('form fields'), and the phrase 'multiple...at once' effectively distinguishes this from sibling tools like 'safari_fill' (single field) and 'safari_fill_and_submit'. However, it stops short of explicit sibling differentiation or scope details that would make it a 5.

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 implies usage ('multiple form fields') but provides no explicit guidance on when to choose this over 'safari_fill' (single field) or 'safari_fill_and_submit', nor does it mention prerequisites like page state or element visibility.

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