capcut_add_text

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

With no annotations, the description must disclose behavioral traits, but it only mentions the prerequisite for a text template. It fails to state that this operation mutates the draft, whether it requires explicit saving via capcut_save, or what happens if the draft lacks a text layer.

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 two sentences and front-loads the purpose, with no filler. It efficiently communicates the core action and a key prerequisite, though at the cost of omitting many details.

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 tool with 9 parameters, no annotations, and no output schema, this minimal description is insufficient. It lacks parameter semantics, side effects, prerequisites beyond the template, and usage conditions, making it inadequate for correct invocation.

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 only 11% (only 'color' has a description). The description adds one semantic clue: the draft must be a text template. However, it does not explain the meaning of text, atSec, posX, posY, durSec, fontSize, trackIndex, or the relationship between these parameters and the overlay behavior.

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 'Add a text overlay' with a specific verb and resource, distinguishing it from sibling tools like add_video and add_image. The additional note about requiring a text template reinforces the tool's specific scope.

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: it is for adding a text overlay and requires a text template (a draft with a text layer), referencing CAPCUT_TEMPLATE_DRAFT. However, it does not explicitly mention when not to use the tool or name alternatives, so it stops short of a 5.

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