live_rename_marker

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

With no annotations, the description does real work: it discloses that the operation targets the running application (in-memory, not the saved song) and that it is a single-step undoable mutation, which is exactly the risk information an agent needs. It stops short of describing failure behavior when the marker reference is invalid or when the new name collides with an existing one.

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?

Two compact sentences, front-loaded with the action and scope, with the undo note last. Nothing is repeated from the schema and no sentence is filler.

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 two-parameter tool with no output schema and no annotations, the description supplies the essentials: what it mutates, where, and how to reverse it. Remaining gaps are edge-case behavior (invalid reference, duplicate name) rather than anything blocking a correct first call.

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%, so the description must compensate, and it does for the ambiguous parameter: it explains that 'marker' accepts either an integer index (per live_markers numbering) or the marker's current name, resolving the anyOf that the schema leaves unexplained. The 'name' parameter is only implicitly characterized as the new name, not as a replacement value constrained to be unique.

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 (rename a marker) plus the target environment (running Studio One), and clarifies the identifier forms accepted. It also names live_markers as the source of the numbering scheme, so it is distinguishable from live_add_marker and live_delete_marker without opening any schema.

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?

Usage is implied rather than stated: it signals the tool acts on a live session and that live_undo is the reversal path. It never says to call live_markers first to discover valid indexes, nor when to prefer renaming over deleting and re-adding a marker.

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