generate_video

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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description adds genuine value by revealing this is an asynchronous job that must be polled rather than a synchronous return. However it says nothing about what allow_network actually permits, whether the render consumes credits/time, or what happens on failure – notable gaps for an open-world mutation tool.

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?

One compact clause pair with the action front-loaded and the follow-up step appended; nothing is wasted. It is arguably too terse for a tool with two undocumented parameters, but that is a completeness issue rather than verbosity.

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 no explanation, and the async polling instruction covers the main workflow need. The unexplained allow_network flag and absent preconditions leave real gaps for a job-starting mutation tool with open-world access.

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 0%, so the description carries full burden, yet it only vaguely gestures at storyboard_id via 'the selected storyboard' and never explains allow_network at all – the single most non-obvious parameter given openWorldHint=true. Format and expected value of storyboard_id are also unstated.

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+resource ('Start an exact-duration render of the selected storyboard') and explicitly names the sibling to poll (get_video_status), separating it from preview_storyboard, cancel_video and get_video_results in the sibling list.

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?

Clearly implies the call is the kickoff step of an async flow and names the follow-up tool (get_video_status). It does not state prerequisites (e.g., that a storyboard must first be created and its scenes selected) or when to prefer preview_storyboard instead, so no explicit exclusions.

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