capcut_read_timeline

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

With no annotations, the description carries the disclosure burden. It adds a meaningful behavioral trait by stating that the result includes pending unsaved edits from this session, which is important context for an agent deciding whether to trust the returned data as current. The verb 'Read' signals a non-mutating operation, though error behavior and access prerequisites are not covered.

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?

Two sentences, front-loaded with the core action, with every clause earning its place. The return contents are compactly listed in parentheses and the unsaved-edits caveat is stated in a second short sentence with no 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?

For a one-parameter read tool with no output schema, the description gives a strong inventory of the returned data and the key session caveat. It is mostly complete for invoking the tool correctly, though it would be stronger if it explained where the 'draft' identifier comes from.

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 schema has 0% description coverage and the only parameter is an undocumented 'draft' string. The description merely says 'a draft,' which adds no meaning beyond the property name; it does not clarify whether draft is an ID from capcut_list_drafts, a path, or some other identifier.

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 opens with a specific verb and resource ('Read a draft') and enumerates exactly what will be returned: canvas, fps, tracks, and every segment with id/media/times/layer. This makes the tool's purpose unambiguous and visually distinct from siblings like capcut_list_drafts.

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 phrase 'Reflects any pending unsaved edits from this session' provides clear context for when this tool is relevant: when the agent needs the current in-session state of a draft. However, it never explicitly says when to prefer this tool over alternatives such as capcut_list_drafts or capcut_save, so it stops short of full routing guidance.

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