ensure_layers_present

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

No annotations are provided, so the description must fully disclose behavior. It fails to state whether cels are created conditionally, what happens to existing cels, or any side effects. The term 'ensure' is ambiguous without further detail.

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, which is concise, but its vagueness reduces efficiency. Every word should add value; here, 'Ensure cels exist' is not informative enough.

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 4 parameters, no output schema, and no annotations, the description is severely incomplete. It omits return values, error conditions, and behavioral details, leaving the agent with insufficient 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 0%, and the tool definition adds no explanation for parameters. The parameters 'filename', 'layer_names', 'start_frame', and 'end_frame' are listed but not described, leaving the agent to infer their meaning from names alone.

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 'Ensure cels exist for layers across a frame range' is vague; the verb 'ensure' does not specify whether cels are created, verified, or modified. It mentions layers and frame range but lacks specificity to distinguish from siblings like 'create_cel' or 'propagate_cels'.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling list includes many cel-related tools (create_cel, clear_cel, propagate_cels, etc.) but the description offers no context for selection.

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