Start Redshift PNG Sequence

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

With no annotations, the description discloses rich non-obvious behavior: returns job_id immediately, background execution, Beauty-only, never overwrites, job control does not survive server restart, manifest and SHA-256 checks persist. This goes far beyond the schema and gives the agent accurate expectations.

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 dense sentences place the core action first, then prerequisites, then constraints and follow-up tools. Every clause carries operational value without redundancy.

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 side-effecting background job with no output schema, the description covers prerequisites, result (job_id), limitations, persistence, and monitoring tools. It could offer a bit more on the return envelope or error cases, but it is largely complete for correct invocation.

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%, and the description compensates for document_name, render_data_name, output_directory, and frames by adding requirements such as unique naming, PNG format, no AOVs, new parent-existing directory, and 1..300 unique frames. It does not explicitly explain the 'force' parameter, which remains a gap.

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?

Description opens with a specific verb and resource: 'Start a bounded background Beauty-only PNG sequence (1..300 unique frames)', and states the immediate return of a job_id. This clearly distinguishes it from siblings like rs_render or preview_render by emphasizing an asynchronous bounded sequence.

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 enumerates concrete prerequisites (updated bridge, uniquely named open document/RenderData with PNG format, no AOVs, new output directory with existing parent) and explicitly routes follow-up actions to rs_sequence_status and rs_sequence_control. It also warns not to edit the scene during rendering, giving clear when-to-use guidance.

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