Leapfrog MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It partially succeeds by mentioning 'all its data' which implies destructive scope, but it lacks explicit warnings about permanence, irreversibility, or side effects on active browser sessions using that profile.

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?

The single sentence is efficiently front-loaded with the action verb, includes zero redundancy, and every phrase ('saved persistent', 'and all its data') earns its place by distinguishing scope and storage type.

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 the tool's simplicity (single string parameter, no output schema), the description is reasonably complete. It clarifies the deletion scope. However, for a destructive operation without annotations, it could have explicitly noted the permanent nature of the deletion to achieve full completeness.

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?

With 100% schema coverage, the baseline is 3. The description adds minimal semantic value beyond the schema by clarifying that the name refers to a 'persistent browser profile' rather than a temporary session or user profile, reinforcing the parameter's domain context.

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?

The description uses a specific verb ('Delete') with a clear resource ('saved persistent browser profile') and scope ('and all its data'). It effectively distinguishes from sibling tools like profile_list (read) and profile_import_from_chrome (create/import) by emphasizing the destructive removal of 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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as checking profile existence via profile_list or warn against deleting active session profiles. It simply states the action without contextual usage guidance.

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