add_strip_fade

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

With no annotations, the description must carry the behavioral burden. It discloses the visual fade-to-black effect and sound volume fade, but does not say whether existing fades are replaced, what permissions are needed, or what happens if the strip is missing.

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 core behavior is front-loaded in one clear sentence, and the Args/Returns structure is easy to scan. The Returns line is somewhat redundant because an output schema exists, and 'frames keyed' is vague, but the description remains compact.

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 three-parameter strip-fade tool with an output schema and no annotations, the description gives enough to call it correctly: target strip, fade frame counts, visual/sound meaning, and return shape. It could be more complete about side effects and strip-type scope, but nothing critical is missing.

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 usefully explains all three parameters: strip_name identifies the target strip, and fade_in/fade_out are frame counts measured from the strip start and end. The strip_name explanation is still thin, but the fade parameters are well covered.

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 and resource: fade a strip in/out, including the sound-strip volume behavior. It is clear, but does not explicitly distinguish sequencer strips from related strip types such as NLA strips 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?

The description implies when to use it—when a strip needs a fade-in and/or fade-out—but never compares it with alternatives such as set_strip_property or states exclusions. Usage is inferable but not explicitly guided.

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