ae_render_composition

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

With no annotations, the description must carry the full behavioral disclosure burden. It reveals that an automatic export preset is used and that output requires visual review, but it omits other important behavior such as file output, overwrite effects, or whether rendering is synchronous.

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 short, front-loads the core action, and adds an important caveat without waste. However, it is so brief that valuable behavioral and usage context is missing.

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 five parameters, no output schema, and no annotations, the description is incomplete. It doesn't explain what parameters are needed to target a composition, where output goes, what the result looks like, or whether rendering is safe to run repeatedly.

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 only 40%, so the description should compensate for unclear parameters like output_path, output_preset, and format. It only hints at output behavior through 'automatic export preset' and does not clarify parameter roles or relationships.

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 identifies the operation ('Render a composition') and the specific resource type, with the qualifier 'automatic export preset' adding useful scope. It doesn't explicitly distinguish from frame-capture siblings like ae_capture_frame, but the verb 'render' and reference to export presets make the intent reasonably clear.

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 includes a meaningful usage condition: the render must be visually reviewed before delivery. This communicates when the output is not appropriate for final unattended delivery, though it doesn't explicitly name alternatives or state when to prefer a different tool.

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