Enqueue After Effects Render

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

Adds important behavioral disclosure beyond annotations: saves the open project, requires confirmation, and explicitly disclaims rendering/overwriting. Annotations are consistent, so no contradiction, though it could further explain queue persistence or undo semantics.

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 compact, information-dense sentences with the main action front-loaded. No filler or redundant restatement of the title.

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?

Complete enough for a two-parameter tool with full schema coverage and output schema present: it covers side effects, safety, and prerequisite. The phrase 'named host templates' is slightly ambiguous and no explicit alternative routing is provided, preventing a 5.

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 coverage is 100%, with both parameters documented; the description reinforces them via 'exactly one previewed' and 'requires explicit confirmation' but adds no new format or syntax details beyond the 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?

States a specific verb ('Queue'), resource ('After Effects render'), and clear scoping ('exactly one previewed... with named host templates'). It also differentiates itself from rendering tools by explicitly noting it never starts rendering.

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?

Gives clear context: requires explicit confirmation, saves the project, and never starts rendering or overwrites output. It implies the preview prerequisite via preview_token but does not explicitly name sibling alternatives or exclusion conditions.

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