create-adjustment-layer

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states 'Create' but does not describe side effects, such as whether the tool modifies the composition in place, what happens if the composition doesn't exist, or if it returns a reference to the new layer. This lack of transparency is significant for a creation tool.

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 sentence that efficiently conveys the core purpose. No unnecessary words or redundancy. It is appropriately front-loaded with the key verb and object.

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?

Given no output schema and no annotations, the description should explain what the tool returns (e.g., layer ID) or confirm success. It does not. With 6 optional parameters, the description lacks completeness about behavior, error conditions, or outcome.

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%; each parameter has a clear description in the schema. The tool description adds no additional semantic value beyond the schema. With high schema coverage, a score of 3 is appropriate as the description is adequate but not enhanced.

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 action (create) and the resource (adjustment layer) with context of composition. It is distinct from sibling tools like apply-effect or add-marker, as it specifically creates an adjustment layer. However, it does not explain what an adjustment layer is or its typical use case.

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 provides basic usage context: create in a specified composition or the active one. It does not offer guidance on when to use this tool versus alternatives (e.g., when to use create-composition first) or when not to use it. No exclusions or prerequisites mentioned.

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