copy_effects_between_clips

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

Discloses that intrinsic properties like Motion/Opacity are not copied unless specified, but the 'unless specified' part is ambiguous and not reflected in the schema. Does not detail side effects on target clip (overwrite, append) or error conditions.

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?

Two sentences, front-loaded with the core action. Every sentence adds value without redundancy.

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?

No output schema or annotations; description lacks return value indication, error handling clues, and precise behavior on target clip. For a straightforward copy tool, it's moderately complete but missing common behavioral details.

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 100% with descriptions. Description adds context that effect_name is optional and copies all effects if omitted, but does not significantly enrich parameter meaning beyond 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 states 'Copy all effects (or a specific effect) from one clip to another' with a specific verb and resource, and distinguishes itself from siblings like 'copy_effect_values' by scoping to effects list vs values. Also clarifies exclusion of intrinsic properties.

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 explicit guidance on when to use this tool vs alternatives (e.g., 'apply_effect', 'copy_effect_values'). Does not mention prerequisites, exclusions, or when not to use. Agent must infer usage from context.

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