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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description's job is to add beyond that. It does add two genuinely useful facts: the operation is asynchronous and must be polled ('inspect until the accepted delivery file is ready'), and it can consume account credits. However it does not say what the returned export state looks like, how long renders take, or what failure/rejection looks like.

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 short, front-loaded sentences with no filler; the render action comes first and the polling instruction second. The middle clause ('persisted export state') is slightly jargon-y but not wasteful.

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-value detail is legitimately omitted, and the credit-spend warning covers the main operational risk. But with 2 required params at 17% coverage and no alternative-tool routing, the definition is only minimally sufficient for an expensive, idempotency-keyed render call.

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 only 17%, so the description carries the burden of explaining parameters — and it explains none of them. clipId, workspaceId, format, resolution, coverFrameSeconds, and the required idempotencyKey are all undocumented in prose, leaving an agent to guess at identifier sources and the meaning of 'existing-account-supported quality'.

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 and resource ('Render one managed clip') plus the quality constraint tied to the account. It is distinguishable from siblings like clips_create, but it never contrasts itself with exports_start or other export-adjacent tools, so sibling differentiation is only inferred.

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 implies a workflow ('inspect until the accepted delivery file is ready') but never states when to use this tool instead of exports_start, exports_list, or clips_presets_list. There is no explicit when/when-not guidance or named alternative anywhere in the text.

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