add_null_layer

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

No annotations are provided, so the description carries full behavioral disclosure responsibility. The phrase 'Add a null object layer' only names the action; it does not disclose whether the operation is destructive, requires an existing composition, returns the created layer, or where in the layer stack the null is placed. For a mutation operation without annotations, this is a significant transparency gap.

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, efficient sentence with no filler or redundant phrasing. It is well-structured as a concise statement, though the brevity reflects a lack of substantive content rather than deliberate information density.

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 the tool has 3 parameters, no annotations, no output schema, and only 33% schema description coverage, the one-sentence description is far from sufficient. It does not explain how the null layer is added to a composition, which parameter selects the target, or what the expected behavior is. The description is too minimal for an agent to use the tool reliably in the broader API context.

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 only 33%, with only 'name' having a description ('Layer name'); compId and compName are undocumented. The tool description does not mention any parameters or their roles, so it fails to compensate for the low schema coverage. An agent has no way to infer whether compId and compName are alternatives, precedence, or which is required for targeting a composition.

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 'Add a null object layer' uses a specific verb and resource, but it essentially restates the tool name 'add_null_layer' with words. It provides no additional scope or contextual information (e.g., target composition, purpose of a null layer), and while it distinguishes from sibling layer-add tools by naming the layer type, that distinction is already present in the tool name.

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 add_solid_layer, add_text_layer, or precompose_layers. The description does not mention prerequisites like an open project or composition, nor does it explain the relationship between compId and compName as targeting options. No exclusions or alternative tool recommendations are provided.

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