raw_track_move_top

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

With no annotations, the description does some behavioral work by warning that the action may open a dialog or change project state. However, it is vague and defers to 'inspect the command name first' rather than explaining the actual side effects, reversibility, or project-state impact.

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 short and front-loads the purpose in the first clause. The leading 'TrackMoveTop:' is redundant with the tool name, and the trailing caution is vague, but overall every sentence adds some useful context.

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 is simple (no parameters, no output schema), so the description covers the basics: purpose, argument count, and side-effect uncertainty. It still leaves gaps such as prerequisites (focused track), exact meaning of 'top', and whether the operation is undoable, which an agent may need.

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 zero parameters, so baseline is 4; the description reinforces this with 'no-argument'. There is no parameter semantics to clarify beyond the empty schema, so the baseline is appropriate.

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 states a specific action ('Move the focused track to the top') with a clear verb and resource. This semantically distinguishes it from siblings like raw_track_move_bottom, raw_track_move_up, and raw_track_move_down even without naming them.

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 no guidance on when to choose this tool over the many track-movement alternatives or what conditions apply. 'Static no-argument Audacity action' is a constraint, not a usage policy, and no exclusions or alternative routing are provided.

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