add_movie_strip

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about side effects, required context (e.g., a sequencer must exist), or return behavior. The tool likely modifies the scene but no such information is given.

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?

It is extremely short, but this is under-specification rather than conciseness. There is no useful content; the single sentence merely restates the tool name. It could be considered inefficient because it wastes the opportunity to convey actual information.

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 tool that likely modifies the scene by adding a strip, with no annotations, no parameter descriptions, and no indication of return values, the description is completely inadequate. Even with an output schema present, the agent lacks the essential input semantics and behavioral expectations.

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% – none of the parameters (name, channel, filepath, frame_start) have descriptions in the schema. The description does not compensate by explaining what these parameters mean or how they relate to adding a movie strip. An agent cannot correctly construct a call without external knowledge.

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 is 'Blender Studio Pro MCP: add_movie_strip' – essentially repeating the tool name with a product prefix. It fails to state what the tool does. An agent cannot determine that this adds a movie strip to the VSE (Video Sequence Editor) or how it differs from siblings like add_image_strip or add_sound_strip.

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 is given on when to use this tool versus alternatives. The description provides no context about typical use cases, prerequisites, or conditions that would differentiate it from similar sequencing tools like add_image_strip or add_sound_strip.

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