Safari MCP Server

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

No annotations provided, yet description omits critical behavioral details: whether it returns raw HTTP source or live DOM (crucial for SPAs), truncation behavior when maxLength is exceeded, encoding handling, or performance implications of large pages.

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 brief at 5 words with zero redundancy. While efficiently front-loaded, the extreme brevity contributes to underspecification given the tool's behavioral complexity and numerous siblings.

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?

No output schema exists, yet description fails to indicate return format (HTML string?). With 50+ sibling tools including similar extraction utilities, the lack of differentiation guidance and behavioral details leaves significant gaps for agent selection.

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 coverage is 100% with maxLength fully documented ('Max chars (default: 200000)'). Description adds no semantic context beyond the schema, meeting the baseline expectation when structured documentation is complete.

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?

States specific action (Get) and resource (HTML source of current page), distinguishing it from screenshot or interaction tools. However, it fails to explicitly differentiate from sibling 'safari_read_page' or 'safari_analyze_page' which likely extract content vs. markup.

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 no guidance on when to use this versus 'safari_read_page', 'safari_analyze_page', or 'safari_accessibility_snapshot'. No mention of when to use the optional maxLength parameter or typical use cases.

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