ae_renderQueue

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

It adds real behavioral context the annotations don't carry — the 'render' action is blocking and uses the internal renderer, which matters for timeouts. But 'clear (remove all)' and 'remove index' are destructive queue mutations while annotations declare destructiveHint=false; the description undercuts the annotation rather than complementing it. No mention of whether the queue can be recovered or of failure behavior.

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?

A single front-loaded sentence that packs the resource, all four modes, and the two most important behavioral facts (blocking, internal renderer) with no filler.

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 2-param, no-output-schema tool the coverage is reasonable: modes are enumerated and the blocking render behavior is flagged. Gaps remain on return shape for 'list' (no output schema exists to cover it), index base, and what happens when the queue is empty or an index is out of range.

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 0%, so the description has to carry the parameters — and it does partially, by mapping the enum values to operations ('clear (remove all)', 'render now') and tying 'index' to the remove action. It never says whether index is 0- or 1-based, or what error occurs if index is omitted with action='remove', which is the main ambiguity.

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?

Names a specific resource (After Effects Render Queue) and enumerates the four operations it performs: list, clear, remove, render. The parenthetical '(AE internal renderer)' implicitly distinguishes it from the AME-based siblings ae_queueInAME and xapp_renderAEToPremiere, though it never names them.

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 action list implies when each mode applies, but there is no explicit guidance on when to choose this tool over ae_addToRenderQueue, ae_queueInAME, or xapp_renderAEToPremiere. It also doesn't state the precondition that 'remove' only makes sense after a 'list'.

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