ae_create_motion_template

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

With no annotations, the description carries the full behavioral disclosure burden, but it only says a motion graphic is created. It does not disclose whether a new composition is created or an existing one is modified, what side effects occur, whether the operation is destructive, or what state must already exist for the tool to work.

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 a single tight sentence with the verb front-loaded and no fluff. It is concise, but the brevity leaves out important context that would normally be expected for a complex tool with nine parameters.

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 nine parameters, no annotations, and no output schema, this one-sentence description is far from sufficient for an agent to invoke it correctly. It omits required input semantics, composition-target guidance, side effects, and any indication of what the tool returns.

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 33%, with only template_id, comp_name, and comp_index documented in the schema. The tool description adds nothing about the six undocumented parameters (start, end, text, title, subtitle, font_size), and it does not even clarify that template_id is required or how it relates to 'brand-aware' behavior.

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 concrete action ('create') and a specific resource ('reusable, brand-aware motion graphic') with a location ('directly in an After Effects composition'). It is distinguishable from siblings like ae_create_motion_blueprint and ae_build_motion_video, though it does not explicitly say 'template' or clarify the exact relationship between a motion graphic and a motion template.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention the prerequisite of selecting a template via ae_list_motion_templates, nor does it contrast this tool with ae_create_motion_blueprint or ae_build_motion_video, so the agent must infer usage from the tool name.

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