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

Beyond the annotations, it discloses two meaningful traits: it can consume account credits (a cost/side-effect warning) and it is asynchronous with persisted state that must be polled. Idempotency is already carried by annotations and idempotencyKey. It stops short of explaining what the destructiveHint entails.

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 tight sentences with the core action front-loaded, followed by the return/async behavior and the credit caveat. Each sentence carries information with no filler, though the phrasing is slightly dense.

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 needn't be described, and the description does cover cost and async flow. Still, as a credit-spending mutation tool with 6 params at 17% coverage, it omits enough parameter behavior that an agent cannot call it confidently without opening the schema.

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% (just workspaceId's 'UUID string'), so the description must compensate across 6 parameters. It vaguely gestures at quality/format via 'existing-account-supported quality' but never explains format, resolution, coverFrameSeconds, workspaceId, or the required idempotencyKey, leaving most parameters undocumented.

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 and resource ('Render one managed clip') and implies scope via 'one' and 'at an existing-account-supported quality', which separates it from batch/status siblings. However it does not explicitly distinguish itself from exports_start or clips_status_get, so an agent must infer the boundary.

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?

'Returns persisted export state; inspect until the accepted delivery file is ready' implies a polling workflow, which is useful usage context. But it never states when to choose this over exports_start, nor how it relates to clips_delivery_promote or clips_inspect, leaving the selection to inference.

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