freeze_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 explicitly states that freezing renders the track to audio and disables real-time plugin processing, which is key behavioral information. However, it could mention reversibility (already implied) or side effects.

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 very concise at two sentences, front-loads the action and purpose, and contains no extraneous words. Every sentence adds value.

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 existence of an output schema (not shown), the description does not need to explain return values. It covers purpose and behavioral impact but misses explaining the parameter and prerequisites (e.g., track must not be empty). For a simple tool, this is mostly 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%, and the description does not explain the only parameter 'track_index' (e.g., what it refers to, how to obtain it). The parameter name is self-explanatory but the description adds no value, so the agent must infer meaning without guidance.

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 'freeze' and resource 'track' with a specific purpose (reduce CPU usage). It distinguishes from the sibling tool 'unfreeze_track' by mentioning 'Unfreeze to edit again.'

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 clear context for when to use the tool (to reduce CPU usage by freezing a track). It implicitly suggests that unfreezing is needed to edit, but does not explicitly state when not to use or compare to other alternatives beyond unfreeze_track.

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