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. The word 'next' hints at the temporal coupling (future dialog), but lacks disclosure on lifecycle (one-shot vs persistent), timeout behavior, or whether the operation blocks until the dialog appears.

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 concise at nine words in a single sentence. Efficiently front-loaded with the verb phrase. However, the brevity comes at the cost of omitting critical behavioral context, preventing a perfect score.

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 asynchronous nature of dialog handling and lack of output schema, the description should explain the execution model (blocking vs non-blocking) and error conditions. Currently adequate for identification but insufficient for correct invocation without trial and error.

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%, with 'action' and 'text' fully documented in the schema. The description adds no additional parameter semantics, but none are needed given the complete schema documentation.

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?

Identifies the specific target resource (alert/confirm/prompt dialogs) and implies the action (handling via a handler setup). However, 'set up handler' is slightly abstract—it doesn't clarify whether this blocks execution, registers a callback, or configures a default response for future automation.

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?

Fails to specify the critical temporal requirement that this must be invoked BEFORE the dialog appears. No mention of when to use this versus simply dismissing via other automation means, or what happens if no dialog appears.

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