Safari MCP Server

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

No annotations provided, so description carries full burden. Excellently discloses stateful side effects: 'All subsequent commands... will target this tab' and explains the persistent context requiring 're-anchor'. Missing error handling details (e.g., invalid index 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 efficient sentences plus a parenthetical workflow hint. Front-loaded with the core action, followed by prerequisite, scope explanation, and troubleshooting. Zero redundancy.

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?

Appropriately complete for a single-parameter state-setting tool. Explains the persistent context effect, references prerequisite sibling tool, and provides troubleshooting. Minor gap: no mention of invalid index handling or bounds checking.

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 ('Tab index (starting from 1)'), establishing baseline 3. Description adds workflow context referencing safari_list_tabs for obtaining valid indices, but does not augment type, format, or constraints 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?

States specific action ('Switch to a specific tab') with clear mechanism ('by index'). Implicitly distinguishes from siblings like safari_list_tabs (viewing vs. switching) and safari_new_tab (creating vs. switching), though explicit contrasts are not stated.

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 workflow prerequisite ('use safari_list_tabs to see indices') and troubleshooting guidance ('If commands seem to run on the wrong tab, call switch_tab again'). Lacks explicit 'when not to use' exclusions, but the imperative guidance is strong.

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