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

Annotations already cover read-only, idempotent, non-destructive, and closed-world traits. The description adds value beyond them: the non-blocking behavior, the failure path (errorMessage says why and what to do), and the independence from an open editor/project.

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?

Four tight sentences, front-loaded with the return contract, then failure behavior, then the two usage constraints. No filler; every sentence carries a distinct fact.

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 detailed, yet the description still covers success fields and the error case. Prerequisites, non-blocking semantics, and the waiting alternative are all present, making it complete for an agent.

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 0% and there is one required parameter, so the schema alone leaves jobId's role undocumented. The description implies jobId is the export's job ID (referenced via 'its job ID' for wait_for_jobs) but adds no format or sourcing detail; baseline 3 for a single param with light description-level meaning.

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?

States a specific verb (Read) and resource (owned cloud export/render) and enumerates what it returns: status, actual completed frames, and download URL when successful. It also differentiates from wait_for_jobs by declaring it does not block.

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?

Gives clear context (no open editor or project required) and explicitly names the alternative (wait_for_jobs) for the waiting case with the job ID to pass. It does not address when to prefer this over list_renders, but the when-to-use signal is strong.

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