effect_crossfade_clips

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

With no annotations, the description carries the behavioral burden. It discloses the precondition and what operation is performed, but it does not mention whether crossfading is destructive, whether it can be undone, or what happens if the selection does not contain two overlapping clips. This is an adequate but incomplete behavioral disclosure.

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 short sentences front-load the action, then give the essential prerequisite, then confirm the empty parameter list. Every sentence is necessary and there is no filler or repetition.

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 zero-parameter, no-output-schema tool, the description is largely complete: it names the operation, the target, and the required selection. It lacks only edge-case or reversibility details, which would strengthen completeness for a mutating audio effect.

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 tool has zero parameters and the schema coverage is 100%, so there is no parameter semantics to document. The description redundantly confirms 'Takes no parameters,' which aligns with the baseline for a parameterless tool.

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 a specific action ('Crossfade'), the exact object ('the overlap between two adjacent, overlapping clips'), and the required precondition ('Select the overlapping region across both clips first'). This clearly distinguishes it from sibling tools like effect_crossfade_tracks by targeting clips rather than tracks.

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 gives an explicit prerequisite: the overlapping region must be selected before invoking the tool. It does not explicitly name alternatives or state when not to use it, but for a zero-parameter effect the selection guidance is sufficient context for correct use.

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