text_to_video

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

The description discloses the return value (task id, status, output URLs) and mentions RunAPI, but it does not explain the asynchronous nature, potential costs, or any side effects. With no annotations, the description carries the full burden and only partially fulfills it.

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?

The description is a single sentence that front-loads the primary action and return info. It contains no filler or redundant details.

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?

For an 11-parameter tool with no output schema and no annotations, this description is far from complete. It leaves critical gaps around async processing, parameter usage, and interpretation of the task status, making it inadequate for effective tool selection and invocation.

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 only 18%, so the description needed to compensate by explaining parameters. It does not, though it gives a general hint that 'prompt' is the text input. Optional parameters like wait, timeout_ms, and callback_url remain unexplained.

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 action ('Create') and the resource ('Runway task'), with the parenthetical 'text to video' specifying the modality. It distinguishes from siblings like extend_video and get_task by focusing on creation.

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 use for generating a new video from text, but provides no explicit guidance on when to use it vs. alternatives like extend_video or get_task. It does not mention exclusions or the optional waiting behavior.

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