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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only vague context ('owner-scoped', 'access policy also apply') and includes irrelevant pricing boilerplate, without useful behavioral details like status response contents or authentication requirements.

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 text is short but not front-loaded with the tool's actual function, and it includes an irrelevant pricing HTML block that is pure noise. The opening sentence fragment is ambiguous and does not earn its place.

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?

An output schema exists, so return values need not be described, and annotations cover safety. However, for a low-complexity detail tool the description still fails to establish the tool's core purpose or when to use it, leaving a significant contextual gap.

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% and the description never mentions jobId or explains its expected format or source. The description therefore adds no semantic meaning beyond the bare parameter name in the schema.

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 'Owner-scoped local asynchronous job lifecycle' is a vague fragment rather than a specific verb+resource; it never states that the tool retrieves a Firecrawl crawl job by ID. The title 'Firecrawl Crawl detail' helps only marginally and is not reinforced by the description, leaving sibling confusion with post_firecrawl_crawl and get_firecrawl_batch_scrape_job unresolved.

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?

It provides policy statements such as 'Disabling new admission does not disable existing job reads or cancellation' and 'Runtime availability and access policy also apply,' but these are not when-to-use guidance. There is no explicit comparison to alternatives or instruction on when an agent should call this versus other crawl/job tools.

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