ae_list_output_templates

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

With no annotations, the description carries the disclosure burden; 'List' indicates a read-only operation and 'all available' states the scope. It does not clarify whether results include project-specific templates or what the returned structure looks like, but for a zero-parameter list tool this is a moderate gap.

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?

One sentence with no filler; the verb, object, and context are front-loaded. Every word earns its place.

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 no-parameter listing tool, the description states the resource and scope sufficiently for an agent to invoke it. The only missing context is the output shape, but since there is no output schema, a note about return format would have been a small improvement.

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?

The input schema has no properties and the tool takes zero parameters, so there is nothing the description must explain beyond the schema. The 0-parameter baseline applies here.

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 ('List') and a specific resource ('output module templates') in an After Effects context, so an agent can tell what the tool operates on. It does not explicitly contrast itself with the sibling tool ae_list_render_templates, though the resource name makes the distinction 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 usage context is implied: call this when you need the set of output module templates. There is no explicit guidance about when to prefer it over ae_list_render_templates or how it relates to ae_set_output_module, so it stops short of full routing guidance.

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