insert_midi_file

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

With no annotations, the description carries the full burden and does disclose one meaningful behavioral trait: it 'Never overwrites existing items unless replace_existing_in_range is true', which is not derivable from the bare boolean schema. It omits other mutation-relevant behavior such as error handling on ambiguous track names, permission/save-state requirements, and what a dry_run returns.

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?

Three short sentences, front-loaded with the core action and followed by the precondition and the destructive-behavior guard. Nothing is padded, though the middle sentence ('Write the MIDI yourself, then insert') is slightly awkward advice rather than specification.

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 10-parameter mutating tool with nested objects, no annotations, and no output schema, the description covers purpose, precondition, and the one destructive toggle. It still leaves gaps around error behavior, interaction with dry_run, and the fact that only one parameter is required, so it is adequate but not complete.

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 coverage is already 80% and most params (track, position, length, midi_path) are self-documenting, so the baseline would be 3. The description adds real value by explaining the semantics of replace_existing_in_range (the only way items in range get destroyed), which the schema leaves as a bare boolean.

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 ('Insert a .mid file from disk onto a track at a position'), plus the source and destination, so the agent knows exactly what the call does. It does not, however, explicitly distinguish itself from close siblings such as insert_midi_events, insert_riff, or insert_groove, which an agent must infer from the file-on-disk framing.

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?

'Write the MIDI yourself, then insert' implies the required precondition (a .mid file already exists on disk and is passed via midi_path). That is useful context, but there is no statement of when to choose this over insert_midi_events or how it relates to dry_run/verify_change, so routing guidance is only implied.

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