remove_realtime_effect

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

No annotations are provided, so the description itself must convey behavior. It clearly indicates that this is a destructive removal of an effect from the realtime chain, but it does not disclose potential error cases, whether removal is undoable, or what response the caller should expect.

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 concise, front-loads the purpose, and then provides a clear Args block. Every sentence adds value with no redundant or misleading content.

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 removal tool, the description covers the operation and both parameters well enough to invoke it correctly. It is slightly incomplete by not describing return values or invalid-index behavior, but those are not critical for a straightforward removal action.

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 description fully compensates by explaining both parameters: track_id's source and the -2 Master bus special case, and index's source from list_realtime_effects. This adds meaning far beyond the bare integer schemas.

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 states 'Remove one effect from a track's (or the Master bus's) realtime effect chain by index,' using a specific verb and resource. It also distinguishes itself from related siblings like add_realtime_effect, list_realtime_effects, and set_realtime_effect_active.

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 clear context on how to invoke the tool: track_id comes from project_get_info's track list, -2 targets the Master bus, and index comes from list_realtime_effects. It does not explicitly state when not to use this tool or mention alternative tools, but the prerequisites are strong enough for correct use.

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