firecrawl_agent

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

With no annotations, the description must disclose behavioral traits. It only states 'Run an autonomous Firecrawl agent job' without mentioning whether it is synchronous or asynchronous, side effects, authentication needs, or output behavior.

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 a single sentence, which is short but not sufficiently informative. It under-specifies the tool, making it inadequate for an AI agent to understand usage.

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 (autonomous agent with 3 parameters and no output schema), the description is extremely incomplete. It fails to explain what an agent job does, how to use parameters, or what the result looks like.

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 0%, meaning the parameter names and types are the only information. The description adds no meaning to 'urls', 'prompt', or 'schema', leaving their purpose and format unclear.

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 states the tool runs an autonomous Firecrawl agent job, which is a specific verb and resource. However, it is vague about what an autonomous agent job entails and does not distinguish it from sibling tools like 'firecrawl_crawl' or 'firecrawl_extract'.

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 is provided on when to use this tool versus alternatives. The sibling tools include more specific operations, but the description offers no criteria for choosing this agent over them.

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