ableton_import_midi

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

With no annotations provided, the description must disclose behavioral traits. It implies a mutation by importing file content, but lacks details on side effects (e.g., replacing clips, error handling, undoability) or requirements (e.g., existence of target track).

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, concise sentence that efficiently communicates the tool's core functionality without filler or redundancy. It is front-loaded with the action and resource.

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 the 5 parameters and no output schema or annotations, the description covers the main purpose but is incomplete. It does not explain parameter interactions (e.g., what happens if createTracks is true and trackIndex is provided) or what the tool returns upon success or failure.

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 description adds value beyond the input schema by explaining that trackIndex and clipSlotIndex target an existing track/clip slot while createTracks creates new tracks from the file. This clarifies the relationship between parameters, compensating for the 40% schema description coverage.

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 tool's function: importing a MIDI file into a target track/clip slot or creating new tracks from the file. This distinguishes it from sibling tools like ableton_create_midi_clip which creates a clip from scratch, and ableton_modify_track which modifies existing 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 mentions two usage modes (import into existing slot or create new tracks), but does not provide explicit guidance on when to use this tool versus alternatives, nor does it describe prerequisites or disallowed use cases.

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