Reframe video to a new aspect ratio (Luma Ray 2 Flash)

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

Annotations indicate this is not read-only, destructive, or idempotent. The description adds useful behavioral context: credit cost (17 credits per second) and the output type (R2-hosted URL). No contradiction with annotations.

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 front-loaded sentences covering action, parameters, cost, and output. No unnecessary words; every sentence adds value.

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?

No output schema, but description specifies the return (reframed video URL). All parameters are explained, and the cost is mentioned. Sufficient for an agent to understand and invoke the tool correctly.

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%, but the description adds meaning beyond enum values and types: explains videoUrl as public URL, reframeAspectRatio as target ratio from enum, and provides an example for reframePrompt ('extend the sky with sunset clouds').

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 clearly states the tool reframes a video to a new aspect ratio using outpainting/cropping, distinguishing it from the sibling tool aetherwave_reframe_image. The verb 'reframes' and resource 'video' are specific.

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 mentions required parameters (videoUrl, reframeAspectRatio) and optional reframePrompt, but does not provide explicit guidance on when to use this tool vs alternatives like aetherwave_reframe_image. No exclusions or when-not-to-use context.

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