batch_render

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

With no annotations, the description bears full responsibility for behavioral disclosure. It reveals two behaviors: 'No implicit cut' and resumability of failed tasks without redoing completed files. However, it omits critical behaviors such as whether the operation is synchronous or asynchronous, what the wait parameter does, authentication requirements, and the nature of the output or job status. These gaps are significant for a complex batch operation.

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 description is concise—two sentences with no filler. The purpose is front-loaded, and the behavioral notes are compact. While brevity is a strength, it is too terse given the complexity of the tool, sacrificing essential information. Still, as far as structure, it is efficient and readable.

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?

The tool has a highly complex input schema with nested objects (tasks, clips, effects, automation) and no output schema. The description provides almost no context about what mastering entails, expected outputs, job lifecycle, or how to handle errors. An agent would be left guessing at critical details, making this description inadequate for the tool's complexity.

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?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It does not mention project_id, tasks, or wait at all. The description provides no guidance on how to structure the tasks array, what each field means, or how the wait flag affects behavior. This is a total failure to aid parameter understanding.

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's purpose: mastering multiple source assets in one job. The verb 'Master' is specific and the resource 'source assets' is named. It distinguishes this from single-asset operations by emphasizing 'ONE project job', but it does not explicitly differentiate from sibling tools like batch_render_resume or render_start.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description implies it is for multiple assets but does not mention alternatives or conditions that would favor a different tool. It only provides behavioral notes (no implicit cut, resumability) without connecting them to selection criteria.

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