edge_storyboard_plan

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

With no annotations, the description carries the full burden. It discloses the output's content (shots, camera dynamics, transitions, timing), which is useful, but says nothing about whether this is a costly generation call, whether it is deterministic, or what permissions/limits apply. Adequate but incomplete.

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?

A single front-loaded sentence with no filler or repetition. 'director-level' is mild marketing color rather than a functional constraint, but the whole definition is free of bloat.

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 a 5-parameter tool with no annotations and no output schema, the description usefully sketches the return content, which partially compensates. However, it omits pipeline positioning relative to edge_generate_keyframes and edge_compile_video and leaves two parameters unaddressed, so an agent lacks the full picture.

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 60%: title/prompt/shotsCount are documented, while aspectRatio and targetDurationSeconds are not. The description's mention of 'scene shots' and 'timing' only loosely gestures at shotsCount and targetDurationSeconds and adds no format, range, or default-value guidance beyond the schema.

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 gives a specific verb ('Plans') and a concrete artifact ('director-level screenplay and storyboard breakdown'), then enumerates the constituents (shots, camera dynamics, transitions, timing). It is clearly distinguishable from siblings like edge_video_create or edge_compile_video, though it never explicitly names them as alternatives.

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?

'from a raw prompt' implies this is an early planning stage, but there is no explicit when-to-use statement, no prerequisites, and no routing to or away from siblings such as edge_generate_keyframes. Usage is inferable but not stated.

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