Leapfrog MCP

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral context: reveals 30-minute idle timeout policy and per-session idle tracking. However, omits safety profile (read-only status) and whether calling this frequently impacts pool performance.

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 efficiently structured sentences. First sentence front-loads capabilities (stats, usage, sessions). Second sentence provides actionable threshold guidance (30-minute timeout). No repetition of title or name, zero 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?

No output schema provided, but description compensates by enumerating return data: pool stats, resource usage metrics (memory/uptime), session summaries, and idle times. Adequate for a parameterless monitoring tool, though explicit mention of response structure would elevate to 5.

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?

Zero parameters present. With no input requirements, there are no semantic gaps to fill. Baseline score of 4 applies per rubric specification for zero-parameter tools.

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 'Show' with clear resources: 'pool stats, resource usage (memory, uptime), and all active session summaries.' Distinguishes from sibling tools by emphasizing pool-wide scope and system metrics (memory/uptime) versus session-specific tools like 'session_health' or 'session_list_profiles'.

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 actions to take based on output: 'Sessions approaching 30-minute idle timeout should be refreshed or saved.' However, lacks explicit comparison to siblings (e.g., when to use this vs 'session_health' for individual session status).

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