Firecrawl MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists browser sessions and returns an array, but doesn't mention important behavioral aspects like whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what happens when no sessions match the filter. For a 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 appropriately sized and front-loaded: the first sentence clearly states the purpose, followed by a usage example and return information. Every sentence earns its place, with no redundant or unnecessary information. The structure is clean and efficient.

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 complexity (listing browser sessions with filtering), no annotations, no output schema, and low schema description coverage (0%), the description is incomplete. It doesn't explain the return format beyond 'Array of browser sessions', doesn't mention authentication requirements, and doesn't provide context about what browser sessions represent in this system. For a tool with siblings that manage browser sessions, more context is needed.

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 mentions 'optionally filtered by status' which corresponds to the single parameter in the schema. However, with 0% schema description coverage, the description doesn't add meaningful semantics beyond what the enum values ('active', 'destroyed') already imply. The usage example shows the parameter in use but doesn't explain what these status values mean or when to use them.

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: 'List browser sessions, optionally filtered by status.' This specifies the verb ('List'), resource ('browser sessions'), and scope ('optionally filtered by status'). However, it doesn't explicitly differentiate from sibling tools like 'firecrawl_browser_create' or 'firecrawl_browser_delete', which would require a 5.

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 mentions filtering by status but doesn't explain when filtering is appropriate or when other tools like 'firecrawl_browser_execute' or 'firecrawl_browser_delete' should be used instead. The usage example shows how to call the tool 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.