aeroedu_davinci_render_start

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

The description details the behavioral difference between wait=true (wait for completion, report result) and wait=false (return immediately, continue in background). This adds significant context beyond the annotations, which only indicate non-read-only and non-destructive.

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?

Three sentences in Vietnamese, front-loaded with the main purpose. No wasted words, and the structure is logical: purpose, wait behavior, prerequisite.

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?

While the description covers the tool's purpose and wait behavior, it lacks explicit mention of return values (only 'báo kết quả' for wait=true). No output schema exists, so a brief note on what the result contains would improve completeness. Still, given the tool's simplicity, it is largely adequate.

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 description adds meaning to the parameters beyond the schema: it explains that wait=true leads to waiting and reporting result, while wait=false returns immediately. This contextualizes the timeout parameter as well. Schema description coverage is 100%, but the description still adds value.

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 the tool starts the render queue in DaVinci Resolve. It distinguishes itself from sibling tool aeroedu_davinci_timeline_export by noting that the latter is a prerequisite.

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 explicitly instructs to use aeroedu_davinci_timeline_export first, providing clear usage guidance. It also explains the wait parameter options and their implications.

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