fade_audio

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure, yet it only states the core action. It omits critical behavioral details such as fade duration units, whether the operation mutates the input or produces a new file, and what happens when both fade values are 0 (default).

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 a single efficient sentence with the core concept front-loaded and zero filler. It is concise in form, though the brevity reflects under-specification rather than complete coverage.

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 four-parameter tool with no annotations and 0% schema coverage, one sentence is inadequate for reliable invocation. Even with an output schema present, the agent lacks essential information about fade duration units and output_path semantics, making incorrect calls likely.

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 must compensate for four undocumented parameters, but it only weakly maps fade_in/fade_out to the fade-in/fade-out concept. Essential semantics such as time units for the numeric fade parameters and the meaning of an empty output_path default are entirely missing.

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 uses a specific verb ('apply') and specifies the exact operation ('audio fade-in and/or fade-out'), making the tool's purpose immediately clear. The 'audio' qualifier helps distinguish it from sibling fade_video, though the distinction is implicit rather than explicit.

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 provided on when to use this tool versus closely related siblings such as fade_video, crossfade_videos, or adjust_volume. There are no usage conditions, exclusions, or alternative-selection hints, so the agent must guess based on the name alone.

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