batch_render_resume

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions using a pinned snapshot and task settings, but does not disclose side effects (e.g., whether the original job is updated, whether it creates a new job, idempotency), error handling for missing jobs, or any auth/rate-limit requirements. This is a significant gap for a resume 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 a single, front-loaded sentence with no fluff. It efficiently communicates the core purpose. However, it is overly brief, sacrificing needed detail, which is a trade-off. Structurally it is well-formed but incomplete.

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 tool with 3 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the parameters, when to use the tool, or what behavioral outcomes to expect. An agent has almost no information to safely invoke this tool correctly. The complexity is low but the missing context is critical.

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 for the undocumented parameters. It does not mention project_id, job_id, or wait at all. An agent cannot infer what these parameters mean or how they relate to the resume operation. The description adds no value beyond the raw schema.

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 clear verb ('Resume'), a specific resource ('source-audio batch'), and adds context ('using its pinned snapshot and task settings'). This distinguishes it from sibling tools like batch_render, which would start a new batch, and render_start, which likely handles individual renders. However, it does not explicitly name the sibling it is not, so it is clear but not perfectly differentiated.

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?

There is no guidance on when to use this tool versus alternatives. It implies resuming a previously started batch, but does not state prerequisites (e.g., batch must exist, must have a pinned snapshot) or conditions under which to use it instead of batch_render or job_cancel. The agent must infer usage from the word 'resume', which is weak.

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