screenslick_add_transcript_voiceover_to_timeline

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

With no annotations provided, the description carries the full burden. It only states the action but gives no insight into side effects (e.g., whether existing timeline clips are replaced or appended), required permissions, or whether the operation is reversible. This is a significant gap for a tool that modifies the timeline.

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 very concise, containing only one sentence. While it avoids fluff, it is too terse for a tool with multiple parameters and nested objects. Better structure would front-load key behavioral notes and parameter summaries.

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?

Given the tool's complexity (3 parameters, one being a detailed array) and the absence of annotations or output schema, the description is severely incomplete. It fails to explain prerequisites, return values, error conditions, or how the clips array interacts with the source parameter.

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?

The description offers no explanation of parameters beyond hinting at 'transcript or script' as source. The schema has 3 parameters (source, script, clips) with 0% description coverage. The complex 'clips' array with 9 properties is entirely undocumented in the description, making it hard for the AI to construct correct inputs.

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 it adds voiceover clips from either a transcript or a script to the timeline. The verb 'add' and resource 'voiceover clips' are specific. However, it does not differentiate from sibling tools like 'generate_voiceover' or 'preview_voiceover', which could overlap in functionality.

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?

No guidance on when to use this tool versus alternatives. For example, it doesn't clarify whether to use 'generate_voiceover' first or how this differs from 'preview_voiceover'. The description lacks explicit context for when to invoke this tool.

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