Safari MCP Server

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

Discloses implementation mechanism (JS DataTransfer) and side-effect constraints (no focus steal). With no annotations, description carries burden but omits safety classification (destructive vs read-only) and error behavior.

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-written sentences. First contains action, mechanism, and constraints; second provides compatibility context. Zero redundancy, front-loaded.

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 single-parameter action with schema coverage, but missing safety hints (destructive? read-only?) due to absent annotations, and lacks output description.

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 has 100% coverage describing filePath as absolute path with supported formats. Description implies local file requirement but adds no semantic detail beyond schema baseline.

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?

Specific verb 'Paste' with resource 'image from local file', mechanism 'via JS DataTransfer', and scope 'into focused element'. Explicitly distinguishes from clipboard-based siblings by stating 'no clipboard'.

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 selection criteria via constraints 'no clipboard, no focus steal' and compatibility list (Medium, dev.to, etc.). Implies when to use over safari_clipboard_write, though could explicitly name alternatives.

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