Leapfrog MCP

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

No annotations provided, so description carries full burden. Mentions actions (block, mock, log) but doesn't disclose side effects (e.g., that blocking prevents requests from completing, mocking replaces real responses) or rule persistence/scope beyond the sessionId parameter.

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 well-structured sentences with zero waste: establishes purpose, lists capabilities with examples, and provides specific operational syntax. Information is front-loaded and dense.

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?

Adequate for a 7-parameter mutation tool with complete schema coverage. Covers all actions and removal workflow. Minor gap: doesn't clarify success/failure behavior or explicitly note thaturlPatternis conditionally required (though schema documents this).

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% coverage (baseline 3). Description adds value by explaining the semantic relationship betweenaction='remove'andruleId, and provides concrete usage examples (blocking ads/trackers) that contextualize theurlPatternparameter without merely repeating schema fields.

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 verbs (Add/remove, Block, mock, log) and clearly identifies the resource (network intercept rules, requests, traffic). Distinguishes from siblingnetwork_logby emphasizing interception capabilities (blocking, mocking) not just passive logging.

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 explicit syntax guidance for removal ('Use action='remove' with ruleId'), but lacks broader when-to-use guidance versus alternativenetwork_logand doesn't clarify prerequisites for different actions (e.g., when blocking is appropriate vs logging).

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