import_audio_to_arrangement

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

Annotations already declare non-read-only, non-destructive, closed-world behavior. The description adds a meaningful constraint that the destination must be an audio track's Arrangement timeline, which is not stated in the schema or annotations. It does not cover whether an existing clip at the position is overwritten, where the file must live, or how the import interacts with transport state.

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 that identifies the action, the target container, and the locating unit with no filler. Nothing is wasted and no reading is required to reach the core meaning.

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?

An output schema exists, so return values need not be explained, and the description covers destination, payload, and locating unit. Remaining gaps are the path format and index base, which matter given the 0% schema description coverage but are modest in scope.

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 and mostly does not. 'At a beat' hints that position is measured in beats rather than seconds, which is genuinely useful, but path format (absolute vs. relative, allowed extensions) and whether track_index is 0-based are never clarified.

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?

States a specific verb and resource ('Place an audio file on an audio track's Arrangement timeline at a beat') with concrete examples of the payload (vocal take, reference). It does not differentiate from close siblings such as create_arrangement_clip, create_audio_clip, or duplicate_to_arrangement, so an agent must infer the distinction from the name alone.

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?

Usage is implied by the description and the examples ('vocal take or a reference') give a sense of intent, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The agent is left to infer that file-based import is preferred over clip-creation siblings for material already on disk.

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