ae_set_render_settings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not disclose that applying a template overwrites existing render settings, how time_span_start/time_span_duration override the work area, error behavior for an invalid queue_index, or whether the operation mutates project state in a way that is undoable.

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?

A single, tight sentence with clear verb-object structure, front-loaded with the action. Every word earns its place, and there is no fluff or repetition of schema content.

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 mutating tool with no annotations and no output schema, this one-sentence description is insufficient. It omits prerequisites, side effects of overwriting current render settings, what the time-span parameters imply for the work area, return/confirmation behavior, and error handling for out-of-range queue indices. The schema documents parameters well, but the contextual envelope around the operation is missing.

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 100% — every parameter has a meaningful description with examples and defaults (e.g., 'Best Settings', 1-based index, seconds units). Per the rubric, the baseline is 3 when the schema carries the parameter documentation; the description adds no parameter-level meaning beyond what the schema already provides.

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 uses a specific verb ('apply') plus a specific resource ('render settings template') and target ('render queue item'). It clearly differentiates from sibling tools like ae_set_output_module (output module settings), ae_list_render_templates (listing templates), and ae_start_render (starting renders). An agent can identify what this tool does without opening the schema.

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 guidance is given on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., that a queue item must first exist via ae_add_to_render_queue) or clarify when to choose render settings rather than output module settings (ae_set_output_module). With 60+ siblings, the agent is left to infer all context.

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