ae_render_frames

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

No annotations are provided, so the description carries the full burden. It mentions output (saved file paths) and default temp directory, but lacks details on whether rendering is synchronous, whether it overwrites existing files, or if it requires specific permissions. This is adequate but incomplete.

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?

Two concise sentences: first states purpose and use case, second states return value. No extra words, front-loaded with key information.

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 4 parameters (1 required) and no output schema, the description is somewhat incomplete. It explains the purpose and return format, but does not describe the 'comp' parameter or the 'prefix' parameter's purpose. Gaps remain, but the core concept is clear.

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 50%; the description adds context for times ('range of times') and output ('PNGs'), but does not explain the 'comp' or 'prefix' parameters beyond what the schema provides. The value added over the schema is minimal.

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 verb 'Render', the resource 'several frames of a composition', and the output format 'PNGs'. It also distinguishes itself from siblings like ae_render_frame (single frame) and ae_render_comp (whole comp) by specifying 'several frames' and 'range of times'.

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 provides a clear use case: 'to review motion across a range of times'. While it does not explicitly state when not to use it or name alternatives, the sibling list includes ae_render_frame for single frames, making the distinction implicit.

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