effect_crossfade_tracks

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

With no annotations, the description carries the full behavioral burden. It does disclose prerequisites (overlap and selection) and the nature of the operation (crossfade). However, it does not state whether the effect modifies the original tracks destructively, whether it is undoable, or what happens to the selection afterward. The steps add useful behavioral context but leave the safety/impact profile unclear, which is typical for an effect tool without annotations.

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 two concise sentences with no filler. The purpose is front-loaded, followed by actionable steps. Every word contributes meaning, making it highly efficient and well-structured.

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?

Given that the tool has no parameters, no output schema, and minimal complexity, the description covers the essential invocation details: what it does and how to prepare for it. It could optionally mention the relationship to effect_crossfade_clips or clarify that the crossfade replaces the overlapping section, but these are minor omissions. The description is adequately complete for an agent to call the tool correctly.

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 is already fully covered (100% coverage with an empty properties object). Per the rubric, a tool with no parameters gets a baseline of 4. The description adds no parameter-specific detail because none exists, which is appropriate; the baseline holds.

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 states the action (crossfade) and the resource (two overlapping tracks), with a specific verb-noun pairing. It naturally distinguishes itself from the sibling effect_crossfade_clips by specifying 'tracks' rather than clips, so an agent can tell them apart without inspecting schemas.

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 provides clear usage steps: align tracks to overlap, select both, then run. This establishes the precondition and the exact invocation sequence, but does not explicitly mention exclusions or alternatives (e.g., when not to use, or that effect_crossfade_clips exists). Since it gives clear context without exclusion, it earns a 4, not a 5.

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