create-adjustment-layer

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure, but it only states the core action without detailing side effects like adding a layer to the composition's stack or the layer's effect on underlying layers. It also omits prerequisites, reversibility, or any impact on existing layers.

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?

The description is a single, front-loaded sentence that communicates the essential information without any filler. It is appropriately sized for the tool's simplicity and immediately conveys the action and target resource.

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?

The schema richly documents all parameters, making invocation possible, but the description lacks broader context such as what an adjustment layer does in a composition or how this fits into a workflow. With no output schema and no annotations, the description alone provides minimal contextual guidance beyond the core action.

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?

All parameters (6) have schema descriptions with defaults and units (e.g., name default, size defaults to comp dimensions, duration in seconds), resulting in 100% schema coverage. The description adds no additional parameter meaning, aligning with the baseline for high schema coverage.

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 clearly states the tool creates an adjustment layer in a specified composition or the active comp, using a specific verb and resource. It distinguishes this from sibling tools like create-text-layer or create-composition, which create different entities or layers.

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 implies when to use the tool (when an adjustment layer is needed) and mentions the target composition, but it does not explicitly contrast with alternatives or state exclusions. There's no mention of other layer creation tools, so the guidance is clear only through the tool's name and primary action.

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