firecrawl_scrape

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

No annotations provided, so the description must fully disclose behavior. It mentions 'x402-aware' but does not explain what this means for the agent (e.g., payment implications, rate limits, or failure modes). No mention of side effects, auth needs, or results.

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?

Single sentence with no wasted words. Front-loaded with the essential action (scrape a single URL) and key differentiator (x402-aware). Efficient and to the point.

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 (8 params, nested objects, no output schema, no annotations), the description is far too sparse. It does not cover the various parameters, their defaults, or expected output. The agent would lack sufficient context to use the tool 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?

Schema coverage is low (38%), and the description adds no new parameter information beyond the schema. It only references 'fetch' indirectly. The meaning of stage, options, distribution, payment_method, etc., remains unexplained, leaving the agent without context for correct usage.

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 clearly states 'Scrape a single URL', a specific verb+resource. It also mentions 'licensed fetch (x402-aware)', which hints at a distinguishing feature. Among siblings like firecrawl_crawl (multiple URLs) and firecrawl_search, this tool's singular focus is clear.

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 guidance on when to use this tool versus alternatives like firecrawl_extract or firecrawl_map. No exclusions, prerequisites, or context for when 'licensed fetch' is appropriate. The description does not help in decision-making.

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