Leapfrog MCP

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

No annotations provided, so description carries full burden. Discloses specific health checks performed ('browser connected, page responsive'). Missing safety profile (read-only implied but not stated), return format, error conditions, or 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?

Three efficient sentences. Main purpose front-loaded. Each fragment earns its place: health criteria, parameter behavior, and usage context. No redundancy or waste.

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?

Low complexity (1 optional param, simple operation) but lacks output schema. Description omits return value structure (boolean? status object? error codes?), which is needed given no output schema exists.

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 coverage is 100% (baseline 3). Description adds reinforcement of the bulk-check behavior: 'Omit sessionId to check all sessions' clarifies the optional parameter's effect better than schema's terse 'Omit to check all'.

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?

Specific verb 'Check' + resource 'session' + scope 'healthy (browser connected, page responsive)'. Clearly distinguishes from siblings like session_create (creates), act (performs actions), or pool_status (pool-level vs session-level).

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?

Explicitly states 'Omit sessionId to check all sessions' (clear parameter usage) and 'Quick diagnostic for debugging' (when to use). Lacks explicit comparison to alternatives like session_list or pool_status for when NOT to use.

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