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

With no annotations provided, the description carries the full behavioral burden. It discloses that the job is asynchronous, reports queued and terminal substates, lists the three terminal statuses, explains the unknown-read reason_code, and provides a concrete retry/polling constraint. This is rich, actionable behavioral context.

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?

Three dense sentences cover the target, the status model, the unknown-read behavior, and retry safety without filler. Critical information is front-loaded from the first sentence, and every clause earns 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?

Even without annotations or an output schema, the description gives enough for an agent to call the tool, interpret terminal statuses, handle unknown reads, and decide when retrying is safe. No missing information appears necessary for correct invocation or basic response interpretation.

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 100%, so the baseline is 3. The description adds meaningful extra semantics by specifying that the quote_job_id must come from an authoritative admitted response and explicitly warns against inferring an id after rejection. This goes beyond the schema's simple 'returned by request_provider_estimate' provenance.

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 a specific verb ('Check') and a specific resource ('asynchronous provider-estimate job created by request_provider_estimate'), which clearly distinguishes it from broader status tools like check_request_status. It also names the relevant execution substates and terminal statuses, making the tool's scope unambiguous.

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 clearly implies this tool is for jobs originating from request_provider_estimate, which is the exact context an agent needs. It also gives explicit retry guidance and warns against inferring quote_job_id after rejected admission, but it does not explicitly contrast the tool with sibling alternatives.

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