Inspect After Effects Render Templates

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

The sentence 'It never queues or renders a composition' adds a valuable negative guarantee beyond the readOnlyHint/destructiveHint annotations, clarifying side effects. Combined with idempotent and openWorld hints, the behavioral profile is well-covered, though retrieval failure modes (e.g., empty render queue) aren't mentioned.

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 tight sentences, front-loaded with the action and resource, followed immediately by the side-effect disclaimers. 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?

Output schema exists so return values need not be explained. The description covers scope and non-destructive behavior adequately for a zero-param read tool, but could mention behavior when the render queue is empty.

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?

Zero parameters, so baseline is 4. Nothing to document and the description doesn't need to.

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 (Read) and resource (render and output-module template names) and constrains scope to the first existing render-queue item. This is distinct from siblings like enqueue_after_effects_render or preview_after_effects_render, though it doesn't explicitly name an alternative.

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?

Implies usage by describing what it reads, but doesn't state when to use this versus preview_after_effects_render, inspect_after_effects_template_source, or the enqueue tools. No explicit when/when-not guidance.

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