capcut_list_masks

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

With no annotations, the description itself must convey behavior. 'List' clearly signals a read-only operation, and the stated count of 9 is a useful behavioral detail. It does not describe the return format, but for a 0-parameter listing tool this is a minor gap.

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 entire description is one precise sentence with no filler. It immediately states what the tool lists and how many items are available.

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 trivial 0-parameter listing tool, the description is substantially complete: it identifies the resource and the expected output count. It could be slightly more helpful by noting that the returned mask shapes can be used with capcut_add_mask, but this is not essential 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?

There are zero parameters, so parameter semantics are not applicable. The baseline of 4 applies: no parameter information is needed, and the description does not need to compensate for any undocumented parameters.

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 'List the 9 available mask shapes' uses a specific verb and resource, and even states the exact count. It clearly distinguishes this from sibling list tools like capcut_list_filters and capcut_list_transitions.

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 usage is implied: an agent would call this when it needs to know what mask shapes are available. However, there is no explicit guidance about when to use this versus capcut_add_mask or other siblings, and no mention that it could supply valid values for adding masks.

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