get_audio_transitions_list

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

No annotations are provided, so the description carries the burden. 'Get a list of all available' does imply a complete, read-only enumeration with no pagination, which is useful. But it says nothing about whether the list is project-, sequence-, or application-scoped, or whether it requires an open project.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately terse for a zero-argument list tool, though the terseness borders on under-specification rather than deliberate economy.

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 simple zero-param lister this is close to adequate, but there is no output schema, and the description never indicates what the returned entries look like (names vs. indices/IDs) — information an agent needs to actually use the result in apply_transition. Scope of the listing is also unstated.

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 takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter gaps exist.

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?

Specific verb ('Get') plus a precise resource ('list of all available audio transitions/crossfades'), with 'crossfades' clarifying what an audio transition actually is. The 'audio' qualifier inherently separates it from the sibling get_video_transitions_list, though the description never says so explicitly.

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 statement of when to call this versus get_video_transitions_list, get_audio_effects_list, or apply_audio_crossfade. The only guidance is implied by the name: this is a discovery call whose results presumably feed apply_transition/apply_audio_crossfade, but that linkage is left entirely to inference.

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