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 discloses the auto-detection behavior ('Finds submit button automatically'), which is valuable behavioral context. However, it omits critical behavioral traits: whether this waits for page navigation after submission, error handling if no form is found, or that this is a destructive/mutative operation.

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 exactly two high-value sentences. The first sentence front-loads the core purpose, while the second efficiently covers the optional parameter behavior. No extraneous words or redundant phrases are present.

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 100% schema coverage and the absence of an output schema (meaning return values need not be explained), the description is appropriately complete for a form automation tool. It covers the primary operation and the key optional behavior. A minor gap remains regarding post-submission behavior (navigation, waiting), but this is acceptable given the schema clarity.

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description restates the auto-detection behavior for submitSelector ('if not specified') which mirrors the schema description ('auto-detected if omitted') without adding significant new semantic meaning. It does not elaborate on the fields array structure or CSS selector expectations beyond the schema.

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 compound action using specific verbs ('Fill' and 'submit') and resource ('form'). The capitalization of 'AND' and phrase 'in one operation' effectively distinguishes this from siblings like safari_fill or safari_fill_form that likely perform partial operations.

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 atomic usage ('in one operation') suggesting when to use this versus separate fill+click steps. It provides explicit conditional guidance for the optional submitSelector parameter ('if not specified'). However, it lacks explicit when-not-to-use guidance or named alternatives for partial form filling.

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