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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false; the description adds the crucial behavioral fact that this tool performs no action itself and only returns procedural instructions. That resolves the tension between the 'Export' name and the read-only annotation. The trailing phrase 'CapCut's official API: Partly' is opaque and adds no usable behavioral detail.

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 core message is front-loaded, but the middle is a long run-on clause ('Returns how to do it in CapCut step by step (screens, buttons, fields) and opens nothing by itself; then do it with...'). The closing fragment 'CapCut's official API: Partly.' is dangling and unclear, costing space without earning it.

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?

With zero parameters and no output schema, the description must explain what comes back, and it does: step-by-step screens, buttons, and fields. It also explains the handoff to the browser tools. The only incompleteness is the ambiguous 'Partly' note about the official API, which leaves the agent unsure what that qualifier means.

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 tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies no input is needed.

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 states a specific action and resource (export a draft in the user's own CapCut account) and immediately corrects the likely misreading by saying it 'returns how to do it in CapCut step by step ... and opens nothing by itself.' It differentiates itself from the browser siblings by naming the cotlet_browser_* tools as the follow-up. The framing is slightly roundabout because the name/title imply a direct export action while the text describes a guidance tool.

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?

It gives a clear usage path: call this to get the steps, then execute them with cotlet_browser_* tools in the user's CapCut Cloud Browser. That is explicit enough for an agent to know what this tool is for and what to do next. It does not, however, say when not to use it or how it relates to alternatives such as capcut_list_drafts.

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