mcp_opendaw_compact_tracks

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

With no annotations provided, the description must convey behavioral traits. It does disclose the destructive action ('Removes tracks with no regions') and the parameter scope (unit_index, -1 for all AUs). However, it does not mention whether the action is reversible/undoable, what happens to related automation/sends, or any side effects beyond track removal. The core behavior is transparent enough for a simple cleanup tool, but lacks deeper context.

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 brief and well-structured: an opening statement of purpose, a reference to the underlying API method with a definition, a usage tip, and a parameter explanation. Every sentence adds value, with no redundant or unnecessary 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 tool with one parameter and a clear destructive action, the description covers the essential aspects: what it does, when to use it, and what the parameter means. It does not detail the return value, but an output schema is provided, which likely covers that. Minor ambiguities like 'empty tracks' vs 'tracks with no regions' are immediately clarified, so the description is largely complete.

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 0%, so the description must explain parameters. It does so fully: 'unit_index: Audio unit index (-1 = all AUs).' This clarifies the parameter's meaning and the special sentinel value, which is critical for correct invocation. No additional detail is needed for this single-parameter 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 states the tool's purpose: 'Remove empty tracks from an audio unit (or all AUs).' It gives a specific verb+resource and clarifies that it 'removes tracks with no regions,' distinguishing it from sibling tools like delete_track or delete_region. The scope (specific AU or all AUs) is also explicit.

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 provides a clear usage context: 'Useful cleanup after deleting regions or editing.' This tells the agent when to invoke the tool, though it does not explicitly mention alternatives or when not to use it. Still, the guidance is actionable and relevant.

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