capcut_read_timeline

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

No annotations are provided, so the description carries the full burden. It explicitly states 'Read-only,' a key behavioral trait for safety, and enumerates the returned data (canvas, fps, tracks, segment details). It does not mention error conditions or permissions, but for a read tool this is substantial.

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?

A single, tightly packed sentence that conveys the tool's purpose, scope, and read-only safety guarantee. Every word earns its place, with no filler or redundant repetition of the tool name.

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 simple read tool with no output schema, the description adequately lists the major return components (canvas, fps, tracks, segments with their fields). It is missing edge-case behavior like draft-not-found errors or authentication requirements, but the core functionality is clearly covered.

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 one 'draft' string parameter with no description (0% coverage). The description only says 'Read a draft,' which minimally implies that the parameter is the draft to read, but it does not clarify whether it expects an ID, path, or name, nor provide any format or example.

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 uses the specific verb 'Read' with a defined resource ('a draft') and enumerates the scope (canvas, fps, tracks, segments). This clearly distinguishes it from sibling tools like capcut_list_drafts, which lists drafts rather than reading a single draft's full timeline.

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 by the read-only nature and the explicit content scope, but there is no direct guidance on when to use this tool versus alternatives, nor any mention of exclusions or prerequisites. It does not contrast with capcut_list_drafts or other sibling tools.

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