Safari MCP Server

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

With no annotations provided, the description carries full disclosure burden. It lists extracted data components but omits behavioral traits like read-only safety, whether it waits for page load, triggers events, or return format structure. 'Analysis' implies inspection but doesn't confirm lack of side effects.

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?

Two sentences with zero waste. Front-loaded value proposition ('Full page analysis in ONE call') followed by specific deliverables colon-separated for scannability. Every word 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 0 parameters and no output schema, the description adequately compensates by enumerating all analyzed components (title, meta, links, images, etc.). Minor gap: lacks return value structure/format details that would typically appear in an output schema.

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?

Input schema has 0 parameters, establishing baseline 4. Description correctly omits parameter discussion since none exist, and the empty schema requires no semantic 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?

Description uses specific verb 'analysis' with comprehensive resource listing (title, URL, meta tags, OG, headings, link stats, image stats, forms, text preview). The phrase 'in ONE call' effectively distinguishes it from specialized sibling extractors like safari_extract_links or safari_extract_meta.

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?

Provides clear context with 'Perfect for SEO/audit' indicating ideal use cases. The 'ONE call' phrasing implicitly contrasts with using multiple specialized sibling tools. However, it lacks explicit 'when not to use' guidance or named alternatives.

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