Safari MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate the read-only/safe nature of the operation, the return data format (object vs string), or error handling behavior when keys don't exist. 'Get' implies reading but lacks specific behavioral context.

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 exactly 7 words, front-loaded with the action verb, and contains zero redundant or filler text. Every word earns its place in identifying the operation, resource, and scope.

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 (single optional parameter, clear read operation), the description is minimally adequate. However, lacking both annotations and an output schema, it should ideally disclose the return format (e.g., whether it returns an object, string, or array) to be fully complete.

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?

With 100% schema description coverage for the single 'key' parameter ('Specific key (omit for all)'), the schema adequately documents usage. The description adds no additional parameter context, meeting the baseline expectation for high-coverage schemas.

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 ('Get') and identifies the exact resource ('sessionStorage data') and scope ('current page'). It implicitly distinguishes from siblings like safari_local_storage (different storage mechanism) and safari_set_session_storage (different operation type) by naming the specific storage type and action, though it doesn't explicitly contrast with them.

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 no guidance on when to use this tool versus alternatives like safari_local_storage or safari_set_session_storage. It also doesn't mention the common use case of omitting the key parameter to retrieve all data, though this is covered in the schema.

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