Leapfrog MCP

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

No annotations provided, so description carries full burden. Adds valuable detail that output includes 'auth status', but omits read-only safety confirmation, pagination behavior, or return format structure that would be essential for a zero-parameter tool.

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?

Single efficient sentence with zero waste. Front-loaded with action ('List') and specific modifier ('persistent'), followed by the specific data attribute returned ('auth status').

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?

For a zero-input tool, description adequately covers intent by mentioning 'auth status'. However, lacks output schema and could explicitly confirm it returns an array/list structure or describe what constitutes 'saved' profiles.

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. Per scoring rules, 0 params = baseline 4. Description appropriately acknowledges this is a parameterless list operation.

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?

Clear verb 'List' with specific resource 'saved persistent browser profiles' and detail 'auth status'. The term 'persistent' effectively distinguishes this from sibling 'session_list_profiles' (session-scoped vs persistent storage).

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?

Implies usage through 'persistent' keyword distinguishing from session-based alternatives, but lacks explicit when-to-use guidance, prerequisites, or when to prefer over 'session_list_profiles' or 'profile_import_from_chrome'.

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