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 adds valuable behavioral context by specifying 'captured' (indicating a buffer/stateful operation rather than clearing the browser's native console). However, it omits critical safety information: whether the clearing is destructive/irreversible, what occurs if invoked without an active capture session, and whether this affects persisted logs.

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?

The description is a single, front-loaded sentence of five words. Every word serves a purpose: 'Clear' (action), 'all' (scope), 'captured' (context/prerequisite), 'console messages' (target resource). Zero redundancy or waste.

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 low complexity (zero parameters, no output schema, simple atomic operation), the description adequately covers the primary function. It could be improved by explicitly mentioning the prerequisite of an active console capture session (linking to safari_start_console), but the current description is sufficient for correct invocation.

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 contains zero parameters. Per the scoring guidelines, 0 parameters establishes a baseline score of 4. The description appropriately requires no additional parameter clarification.

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?

The description uses a specific verb ('Clear') and resource ('captured console messages') that precisely identifies the operation. The word 'captured' effectively distinguishes this from sibling tools like safari_get_console (retrieval) and safari_clear_network (different domain), while clarifying it operates on the instrumentation buffer rather than the live browser console.

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?

The description provides implied usage context through the word 'captured,' suggesting this tool requires an active console capture session (likely started with safari_start_console). However, it lacks explicit guidance on when to use this versus alternatives, prerequisites, or whether this is typically used before/after get_console.

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