Reorder timeline elements

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

Discloses that startTimes are recomputed for back-to-back playback and that the tool is blocked in read-only mode. No annotations provided, so the description covers key behaviors adequately, though authorization details are not elaborated.

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?

Three sentences, each adding essential information. No redundancy or filler.

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 description is fairly complete for a mutation tool: covers purpose, parameters, and behavior. However, it does not describe the return value or compare to siblings, which would add 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?

The description adds meaning beyond the schema: explains default track for trackId, default gap value, and omitted element behavior. Schema coverage is 75%, and the description compensates well.

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 that the tool rearranges a track's elements into a given order and recomputes startTimes, specifying the default track. This distinguishes it from siblings like move_timeline_element.

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?

Provides good context: describes how to use (pass ids in order, omitted elements appended) and when not to use (blocked in read-only mode). However, it does not explicitly compare to alternative tools like move_timeline_element.

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