Safari MCP Server

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral context about navigation handling (React Router vs full page loads) and round-trip optimization. However, lacks safety disclosure about clicking side effects, state mutation, or what happens when elements aren't found.

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 sentences with zero waste. First sentence front-loads value proposition (combined operation + efficiency gain). Second sentence adds technical implementation detail. Every word earns its place.

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, so description must explain return values. States 'return the updated page' which is minimally sufficient given the tool name, but lacks detail on format (HTML vs text) or truncation behavior referenced by maxLength parameter. Adequate for a 6-parameter tool but not comprehensive.

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%, establishing baseline 3. Description implies clicking mechanism ('Click an element') and page return without enumerating specific parameters. No additional semantic guidance provided for distinguishing between text/selector/x,y targeting or wait/maxLength usage, but schema is self-documenting.

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-resource combination ('Click an element then return the updated page') clearly defines the dual action. Explicitly distinguishes from siblings by referencing 'separate click+read_page' and explains handling of both React Router and full page loads.

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 clear efficiency rationale ('saves 1 full round-trip') implicitly guiding users to prefer this over the safari_click + safari_read_page combination. Mentions specific technical contexts (React Router vs full page loads) where it works. Could be improved by explicitly stating when to use safari_click alone instead.

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