flatten_track

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

The description implies destructiveness ('convert freeze to permanent audio') but does not explain side effects, reversibility, or required permissions. Since no annotations are provided, the description should carry more behavioral 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 concise: two sentences plus a parameter list. It front-loads the purpose and is free of extraneous 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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential action and prerequisite. However, it omits details like return value, error handling, and whether the operation is synchronous, which would improve completeness.

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?

With 0% schema coverage, the description correctly explains the lone parameter 'track_index' as 'the index of the track to flatten', adding meaning beyond the schema's type-only definition.

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 action ('Flatten a frozen track') and the effect ('convert freeze to permanent audio'), distinguishing it from sibling tools like freeze_track. However, it does not explicitly differentiate from other track manipulation tools.

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 prerequisite ('The track must be frozen first'), which guides proper usage. However, it lacks guidance on when to use this tool vs. alternatives (e.g., when not to flatten, or what to do if the track isn't frozen).

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