effect_crossfade_tracks

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the operation and the curve types, but does not mention whether the effect is destructive, reversible via undo, or what happens to the underlying clips. This is a meaningful gap for an effect that modifies audio.

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 compact and front-loaded with the actual behavior, followed by a clear parameter breakdown. Every sentence earns its place with no filler or 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?

For a single-parameter tool, the description is reasonably complete: it states the operation, the target context, and the parameter options. However, it omits prerequisites such as needing an active selection and two overlapping tracks, and it does not clarify relationship or distinction from effect_crossfade_clips.

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 fully compensates by documenting the only parameter with all meaningful values: 0=Constant Gain, 1 and 2 as Constant Power variants, 3=Custom Curve, plus the default. This provides real value beyond the bare schema field.

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 identifies the operation as a crossfade applied to a selected region between two overlapping tracks. This is specific enough to distinguish it from the sibling tool effect_crossfade_clips, which targets 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 implies the tool is used when you have two overlapping tracks and a selected region to crossfade, but it does not explicitly state when to use this tool versus alternatives like effect_crossfade_clips. No exclusion criteria or alternative routing is provided.

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