capcut_add_track

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'add a new track' and does not explain whether this mutates the draft in memory, requires saving/discarding, creates an empty lane, or has any side effects on existing tracks. The behavior beyond the bare action is opaque.

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 a single front-loaded sentence with no filler and no redundancy. It earns its place by identifying the action and allowed types, though it could have been more informative without much additional length.

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 no annotations, no output schema, and three undocumented parameters, the one-line description is insufficient. The agent is left without key context: what 'draft' refers to, what 'name' means, how effect/filter tracks behave, and what a successful result looks like.

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 compensates very little. It restates the type enum in prose but adds no meaning for 'draft' (the only required parameter) or 'name'. An agent cannot tell what draft refers to or whether name is a label for the new track.

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 names a concrete operation ('Add a new track') and lists the supported track types, so the core action is identifiable. However, it does not distinguish this generic add_track tool from the many sibling add_* tools such as capcut_add_video or capcut_add_audio, nor clarify that this creates an empty track lane rather than adding media content.

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?

No guidance is given about when to use this tool versus alternatives like capcut_add_video, capcut_add_audio, capcut_add_text, or capcut_add_sticker. The description does not state whether this is a lower-level primitive for creating empty tracks or how it relates to the specialized add/apply siblings.

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