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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes the non-obvious behavior that a call without a job returns all jobs, but says nothing about blocking behavior of 'wait', what status values appear, or whether results are cleared after completion.

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?

It is a single front-loaded fragment with zero padding, so nothing is wasted. However, the extreme brevity is under-specification rather than disciplined conciseness, since key behavior is omitted rather than compressed.

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?

With no output schema, no required parameters and a closed-world read annotation, the tool is simple enough that a short description is workable. Still, an agent polling for export completion would benefit from knowing the possible status values and whether 'wait' blocks, neither of which is present.

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 67%, with jobId carrying no schema description at all; the description's '(or all jobs)' partially compensates by implying that omitting jobId lists all exports. The wait and projectId parameters remain explained only by the schema, which is the expected baseline here.

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 names a specific resource (an export job) and the operation (retrieving its status), and it clarifies the scope variant with '(or all jobs)'. It implicitly distinguishes itself from initiation siblings like export_video, but it never names them, so it falls short of full differentiation.

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?

There is no guidance on when to call this versus cancel_export or the export_* initiation tools, nor any advice on polling versus using the wait parameter. The parenthetical hints that omitting jobId lists everything, but that is left to inference rather than stated as usage guidance.

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