edit_item

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the edit is destructive, how unspecified properties are treated, whether parameters combine in one call, or whether the item must exist first — a serious gap for a 17-parameter mutation tool.

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 compact sentence with the operation list front-loaded and no filler. The catch-all 'or otherwise edits' weakens precision slightly but costs nothing structurally.

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?

With 17 parameters, no annotations, no output schema and only 59% schema coverage, the one-line description is not sufficient. It omits which parameters apply to audio versus MIDI, interaction/ordering between move, trim and fade parameters, and any notion of undo or reversibility.

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 59%, and the description's high-level verb list loosely mirrors the parameter groups (move/trim/fade/re-pitch). It adds the useful signal that some parameters are audio-only, but relies on the schema for the rest; baseline 3 fits given partial 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?

States a specific verb (edits) plus an enumeration of the operations it performs (moves, trims, fades, re-pitches) on a bounded resource (audio or MIDI item). An agent can place it apart from create_midi_item, delete_item, split_item and duplicate_item, though those siblings are never named to sharpen the boundary.

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 when-to-use guidance, no prerequisites, and no alternatives named. The only faint signal is 'otherwise edits', which implies modifying an existing item, but nothing tells the agent when to pick this over split_item or duplicate_item.

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