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. It discloses the stateful nature ('Start') and operational constraint ('once per page'), but lacks details on capture persistence across navigation, buffer limits, or error behavior if called multiple times.

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 total, both essential. First sentence front-loads the core action and scope; second sentence provides the critical usage constraint. No redundant or filler text.

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 tool's simplicity (zero parameters, no output schema) and the presence of sibling tools for related operations (get/clear), the description is sufficiently complete. It could be improved by mentioning how to stop capture or whether it persists across page reloads.

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?

The input schema has zero parameters, establishing a baseline of 4. The description appropriately does not attempt to add parameter semantics where none exist, focusing instead on behavioral description.

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?

Description clearly states the specific action ('Start capturing') and resource ('console messages'), explicitly listing the message types captured (log, warn, error, info). It effectively distinguishes this from siblings like safari_get_console (retrieval), safari_clear_console (deletion), and safari_console_filter (filtering).

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 a clear usage constraint ('Call once per page') that prevents misuse and implies the tool is stateful. However, it does not explicitly name sibling alternatives like safari_get_console for retrieval or describe prerequisites (e.g., navigation to page first).

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