flatten_track

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

With no annotations provided, the description carries the full burden. It discloses that the action removes clips and devices permanently and bakes audio, indicating destructive and irreversible behavior. However, it does not mention any permissions, confirmations, or side effects beyond what is stated.

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 a single sentence that front-loads the action and includes all necessary information without any extraneous words. Every word contributes to understanding.

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?

The tool has an output schema (context), so return values are not needed in the description. The description covers the primary effect but does not mention error conditions (e.g., track not frozen) or confirm the outcome. Adequate but could be more 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?

The schema has 0% description coverage and only one parameter (track_index). The description does not mention the parameter or explain its role, leaving the agent to infer that it identifies the target track. This is insufficient given the lack of schema descriptions.

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 verb 'flatten' and the resource 'frozen track', and explains the action: replaces content with frozen audio, removes clips and devices, and bakes audio permanently. This distinguishes it from siblings like freeze_track and unfreeze_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 description implies that the tool should only be used on frozen tracks ('Flatten a frozen track'), but does not explicitly state when not to use it or mention alternatives. No guidance on prerequisites or conditions beyond the track being frozen.

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