Set render quality for a layer in an After Effects composition to best, draft, or wireframe for optimized previews or final output.
Set the render quality of a layer (best, draft, wireframe)
| Name | Required | Description | Default |
|---|---|---|---|
| quality | Yes | Render quality | |
| comp_name | Yes | Composition name | |
| layer_name | Yes | Layer name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the action but does not mention effects on rendering, whether the change is reversible, error cases, or any side effects beyond setting the value.
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 conveys the tool's purpose and value options with no unnecessary words. Every part 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 simple three-parameter setter with full schema coverage, the description is minimally adequate. However, the lack of usage guidance, behavioral context, and any indication of return values leaves small but real gaps for an agent selecting among many sibling tools.
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 100%, with each parameter documented. The description adds the enum values in prose, which echoes the schema rather than providing new semantic depth, so the baseline score of 3 is appropriate.
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 ('Set') and resource ('render quality of a layer'), and enumerates the three possible values. This distinguishes it clearly from the broader ae_set_layer_property and other layer-related tools.
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?
There is no guidance on when to use this tool versus alternatives such as ae_set_layer_property or ae_get_layer_properties. The intended context is implied by the tool name and description, but no exclusions or sibling routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.