Firecrawl MCP Server

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 effectively describes key behavioral traits: it creates a persistent session that 'survives across multiple tool calls', mentions 'code execution via CDP', and specifies what the tool returns (Session ID, CDP URL, live view URL). However, it doesn't mention potential side effects, error conditions, or performance characteristics.

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 well-structured with clear sections (purpose, usage guidelines, arguments, example, returns), front-loaded with the core purpose, and every sentence adds value. The formatting with markdown headers and code blocks enhances readability without unnecessary verbosity.

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 3 parameters with 0% schema coverage, no annotations, and no output schema, the description does an excellent job covering purpose, usage, parameters, and return values. However, it could provide more detail on error handling, session management implications, or integration with sibling tools like 'firecrawl_browser_execute' for a more complete context.

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 0% schema description coverage and 3 parameters, the description compensates well by explaining each parameter's purpose: 'ttl' as 'Total session lifetime', 'activityTtl' as 'Idle timeout', and 'streamWebView' as 'Whether to enable live view streaming'. It also provides value ranges for the numeric parameters, adding meaningful context beyond the schema's minimum/maximum constraints.

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 tool's purpose with specific verbs ('Create a persistent browser session') and resources ('for code execution via CDP'), and distinguishes it from sibling tools by explicitly contrasting with 'firecrawl_scrape' for simple page scraping. It provides a comprehensive understanding of what the tool does beyond just the name.

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 includes explicit 'Best for' and 'Not recommended for' sections, providing clear guidance on when to use this tool versus alternatives like 'firecrawl_scrape'. It also mentions use cases like 'multi-step browser automation' and 'persistent sessions', helping the agent understand appropriate contexts.

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