live_add_track

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 disclose one useful trait, the default type (audioMono), but says nothing about side effects, whether the new track becomes selected, undo behavior, or that a Studio One connection/session is required.

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?

One compact sentence with the verb, target, and value set front-loaded; no filler. It is efficient, though the parenthetical type list makes the tail slightly dense.

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 simple one-optional-parameter creation tool with no output schema, the description covers what gets created and which variant. It would be fully complete with a note on the open-song prerequisite and what happens to the new track.

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 0%, but the single parameter is an enum whose values the description simply repeats. It does add one piece of meaning the schema lacks, the '(default)' annotation on audioMono, which is genuinely helpful for an optional parameter.

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 ('Add a track') plus the scope ('the song open in Studio One'), and enumerates all five creatable track types. An agent can tell exactly what this does and can distinguish it from sibling tools like live_delete_marker or live_select_track.

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 phrase 'song open in Studio One' implies a prerequisite (an open song) but never states it as a condition, and there is no guidance on when to pick this over siblings or when-not to use it. Usage is only implied, not spelled out.

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