Leapfrog MCP

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

No annotations exist, so description carries full burden. Discloses critical runtime behaviors: BrowserContext isolation model ('no cookie leakage'), concrete pool limit (15), auto-expiry (30 min), return value format (s_k3m7x1), and resource management requirements.

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?

Six sentences, zero waste. Structure front-loads the action, followed by return value, isolation guarantee, resource limits, expiry policy, and operational pattern. Each sentence delivers distinct, essential information for a stateful resource constructor.

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?

Comprehensive for a complex 17-parameter initialization tool with no output schema. Covers creation contract, return format, isolation semantics, resource constraints, and maintenance patterns—sufficient for correct agent operation without external documentation.

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 has 100% description coverage, establishing baseline 3. Description adds conceptual framing ('isolated browser session with its own cookies and state') that contextualizes the 17 configuration parameters but does not elaborate on individual parameter semantics beyond the schema.

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 opens with specific verb+resource ('Create a new isolated browser session') and distinguishes from siblings by explaining it returns a session ID 'to pass to all other tools', establishing it as the prerequisite entry point for the browser tool suite.

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 operational guidance on keep-alive patterns ('periodic navigate or snapshot') and lifecycle constraints (pool limit, expiry). Lacks explicit comparison to sibling session_* tools (e.g., session_health), but clearly signals it must be called first via the session ID reference.

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