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 reset behavior and available profiles, but omits key behavioral context such as whether throttling persists across page navigations, affects all browser tabs, or requires specific permissions.

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?

Three sentences efficiently convey purpose ('Simulate slow network conditions'), configuration options ('Profiles... Or custom'), and teardown ('Call with no args to reset'). Every sentence earns its place with 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?

The description adequately covers the throttling functionality and reset mechanism, but given the lack of output schema and annotations, it falls short of fully preparing an agent for side effects. It omits what the tool returns upon invocation and the scope of the network simulation (global vs. tab-specific).

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?

While the schema has 100% coverage documenting each parameter, the description adds crucial semantic meaning regarding the zero-argument invocation ('Call with no args to reset'). This explains behavior that the schema structure alone does not convey, given that no parameters are marked as required.

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 opens with the specific verb 'Simulate' and resource 'network conditions', clearly distinguishing this throttling tool from siblings like safari_network (monitoring) or safari_clear_network (log management). It further specifies the scope via profiles and custom options.

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 explicit guidance on how to reset/clear the throttling ('Call with no args to reset'), which is critical given all parameters are optional. However, it lacks explicit guidance on when to choose preset profiles versus custom latency/speed values.

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