Firecrawl MCP Server

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

No annotations are provided, so the description carries full burden. It states the tool 'destroys' a session, implying a destructive operation, but doesn't clarify what destruction entails (e.g., irreversible deletion, cleanup of resources, impact on ongoing processes). It mentions a 'success confirmation' return but gives no details on format or potential errors. For a destructive tool with zero annotation coverage, this is insufficient.

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 description is extremely concise and well-structured: a clear purpose statement followed by a usage example and return note. Every sentence earns its place, with no redundant information. It's front-loaded with the core action, making it easy to scan.

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 this is a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical details: what 'destroy' means operationally, error conditions, prerequisites (e.g., session must exist), and the format of the 'success confirmation'. For a tool that permanently removes resources, more context is needed to use it safely and effectively.

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?

The description doesn't explicitly discuss parameters, but the usage example implicitly clarifies that 'sessionId' identifies the session to destroy. With 0% schema description coverage and only 1 parameter, the example adds meaningful context beyond the bare schema. However, it doesn't explain where to get the sessionId or its format, leaving minor gaps.

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 clearly states the action ('Destroy') and resource ('browser session'), making the purpose immediately understandable. It distinguishes this tool from siblings like firecrawl_browser_create and firecrawl_browser_list by focusing on deletion rather than creation or listing. However, it doesn't explicitly mention what 'destroy' entails compared to alternatives.

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. It doesn't mention prerequisites (e.g., needing an existing session from firecrawl_browser_create), consequences of deletion, or when not to use it (e.g., if the session is still in use). The usage example shows how to call it but doesn't provide contextual guidance.

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