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 of behavioral disclosure. It successfully establishes the state dependency (requires prior start_console call) but fails to disclose other critical behavioral traits: whether retrieval clears the buffer (destructive read), message formatting, pagination limits, or idempotency.

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 efficient sentence that front-loads the core action ('Get captured console messages') and appends the critical prerequisite parenthetically. Zero wasted words; every element earns its place.

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 absence of an output schema, the description should ideally characterize the return value format or structure. While the prerequisite instruction adds necessary context, the description remains incomplete regarding what the tool returns (array, string, object?) and buffer behavior post-retrieval.

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 tool has zero parameters (empty input schema), which per evaluation rules establishes a baseline score of 4. No parameter semantics are needed or provided.

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 tool 'Get[s] captured console messages' with a specific verb and resource. The parenthetical prerequisite effectively distinguishes this from sibling console tools like safari_clear_console or safari_console_filter by establishing the required workflow dependency.

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 usage guidance by stating the prerequisite 'must call safari_start_console first,' which defines when the tool is applicable. However, it lacks explicit guidance on when to use this versus alternatives (e.g., safari_console_filter) or whether messages accumulate between calls.

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