Firecrawl: Scrape

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds that output is markdown-oriented with metadata, but it omits crawl-mode cost/latency implications, pagination behavior, and whether output is truncated.

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?

Two sentences, zero filler, with the core action and return shape front-loaded. Every clause earns its place; nothing is padded or restated from the title.

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?

For a read-only fetcher with no output schema, the description should at minimum clarify the return payload and its relationship to firecrawl_crawl/firecrawl_search. It partially does the former but leaves the sibling overlap and crawl-mode behavior unexplained, so it is adequate but incomplete.

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 description coverage is 100%, so url, mode (with its clean 'scrape vs crawl' explanation), and maxPages are fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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?

States a specific verb (scrape/crawl) and resource (URL) plus the return shape (markdown-oriented content and metadata), which is better than a tautology. However, it doesn't differentiate from the sibling firecrawl_crawl, even though this tool also performs crawl mode via the mode parameter, creating ambiguity an agent must resolve by opening schemas.

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?

No when-to-use guidance is given. Nothing tells the agent when to pick this over firecrawl_crawl or firecrawl_search, despite those siblings existing and overlapping. The mode enum in the schema is the only hint, and it lives outside the description.

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