MCP Safari Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the core action (starting monitoring with optional sending to Claude Code) but lacks details on permissions needed, whether it runs continuously, how errors are formatted, or any rate limits. It adds basic context but misses deeper behavioral traits like error handling or resource usage.

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, well-structured sentence that efficiently conveys the tool's purpose and optional feature without unnecessary words. It is front-loaded with the main action and avoids redundancy, making it easy to parse and understand quickly.

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 moderate complexity (starting a monitoring process with parameters) and no annotations or output schema, the description is minimally complete. It covers what the tool does but lacks information on return values, error conditions, or operational constraints. For a tool that initiates monitoring, more context on behavior and outputs would be beneficial.

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%, so the input schema already fully documents both parameters ('autoSendToClaude' and 'interval') with descriptions and defaults. The description does not add any additional meaning or clarification beyond what the schema provides, such as explaining the implications of sending errors to Claude Code or typical interval values. Baseline 3 is appropriate as the schema handles parameter semantics adequately.

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 clearly states the specific action ('Start monitoring Safari for JavaScript errors') and the optional functionality ('and optionally send them to Claude Code'). It uses precise verbs ('Start monitoring', 'send') and identifies the target resource ('Safari', 'JavaScript errors', 'Claude Code'), making the purpose immediately understandable without ambiguity.

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 implies usage context by specifying 'Safari' and 'JavaScript errors,' which helps distinguish it from general monitoring tools. However, it does not explicitly state when to use this tool versus alternatives like 'stop_error_monitoring' or 'get_console_logs,' nor does it provide exclusions or prerequisites for use, leaving some guidance gaps.

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