track

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

No annotations are present, so the description carries the full disclosure burden. It usefully states that all mutations run in a REAPER undo block, supports dry_run, and that delete is destructive. These are valuable behavioral traits that would not be obvious from the schema. However, it omits other side effects (e.g., whether select changes the current project selection) and what the tool returns, leaving some transparency gaps.

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 two sentences long, front-loads the list of supported operations, and follows with the most critical behavioral warnings. Every sentence earns its place with no redundancy.

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 tool with 17 parameters, one enum, and no output schema or annotations, this description is too minimal. It does not map actions to their required parameters (e.g., rename needs name and new_name; set_color needs a track selector and color object), nor does it explain the precedence among the five track-selection parameters. The schema covers some of this, but the description should summarize the selection rules and per-action parameter usage to make the tool reliably callable.

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 schema only describes about half of the parameters, so the description needs to compensate. It does add units for volume (dB) and range for pan (-1..1), which are absent from the schema. But it does not explain the semantics of new_name, mute, solo, armed, select, or how parameters map to actions, leaving significant gaps for a polymorphic tool.

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 identifies the tool as handling track operations, listing the specific actions it can perform (add, delete, rename, select, set_volume, set_pan, mute, solo, arm, set_color). This differentiates it from sibling tools focused on mixing, transport, FX, or markers. However, it is phrased as a domain label rather than a verb+resource statement, leaving a small ambiguity about the exact effect on 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 gives two usage cautions (dry_run for preview, delete destructive) but does not explain when to choose this tool over siblings such as batch or raw_command, nor does it state prerequisites like needing a target track identifier. There is no explicit guidance about which operations to use for which scenario, so the agent must infer usage from the schema.

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