after_effects_render

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

Beyond the annotations (which only say not read-only, not destructive, not open-world), the description discloses concrete runtime behavior: a 300s/8GiB cap, launching an external aerender process, isolation from the artist's AE instance, writing into a new directory, and aborting on license/account prompts. It does not say what state is left behind on timeout or failure, but the operational profile is unusually well disclosed.

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?

Dense and front-loaded: the core action and its limits open the description, with constraints following. A few lines are cryptic or marginally relevant (e.g. 'Never reuses an artist's AE instance'), but there is little 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?

Return values are covered by the output schema and the resource caps are stated, but for a tool whose only required input is an opaque 'recipe' the description leaves the most consequential detail — the recipe format and failure semantics — unaddressed. Adequate for calling, not for calling correctly on the first try.

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% and both parameters are undocumented strings. The description hints at content (recipe carries dependencies, FPS and output-module declarations; directory is a new PNG destination) but never specifies the recipe's encoding or structure, so an agent still cannot construct a valid value from this text.

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 first sentence gives a specific verb and resource — launch aerender for one declared AEP comp/range into a new PNG directory — with scope limits. It is unmistakable what the tool does, though the abstract 'recipe' concept is not defined, leaving the mechanism slightly opaque.

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 description states preconditions (caller must supply timing/dependency declarations, recipe must declare dependencies, FPS and an existing straight-alpha RGBA PNG output module) and a stop condition (license/account prompt). It does not say when to prefer this tool over another or what to do if the preconditions are not met, so usage is implied rather than directed.

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