rename_track

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and it discloses nothing. It does not say the operation mutates project state, whether it is undoable, what happens if trackIndex is out of range, or what the response contains.

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 words are certainly front-loaded and waste nothing, but this is under-specification rather than conciseness. The sentence does not earn its place by adding any information beyond the name and title.

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?

For a 3-parameter mutation tool with no annotations, no output schema, and an undocumented "name" field, the description is far too thin. An agent cannot confirm scope (track in which sequence?), error behavior, or return value from this definition.

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 coverage is 67%: trackType and trackIndex are documented in the schema, but "name" has no description anywhere, leaving it ambiguous whether it is the new name or a lookup key. The description adds no parameter meaning at all, so it fails to compensate for the one undocumented field.

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 concrete verb and resource ("Rename a track"), so an agent immediately knows the operation. It offers no differentiation from the many similarly-named siblings such as rename_sequence, rename_clip, and rename_project_item, which is the only thing keeping it from a 5.

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?

There is no guidance on when to use this versus rename_sequence or rename_clip, nor any mention of prerequisites such as an open project or an active sequence. The agent must infer everything from the tool name alone.

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