pencil2d_add_frames_batch

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

With no annotations, the description carries the full behavioral burden and falls well short. 'In a single operation' hints at batching but doesn't state atomicity, whether existing keyframes at those indices are overwritten, whether the .pclx must already exist, or what happens on partial failure.

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 with no filler, correctly leading with the batch verb and the two input sources. It is efficient, though its brevity is also the source of the behavioral gaps.

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 six-parameter mutation tool with no annotations and no output schema, the description leaves the agent without mutation semantics (overwrite behavior, ordering, failure handling) or any indication of what is returned. Rich schema coverage offsets this only partially.

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%, so all six parameters including the nested frame object fields are documented in the schema; baseline 3 applies. The description adds only the high-level list-vs-directory framing and no syntax, format, or precedence details beyond the schema.

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 gives a specific verb ('batch insert'), resource ('multiple animation keyframes'), and dual source modes ('from a list or directory'), which distinguishes it from the singular sibling pencil2d_add_frame. It stops short of naming that sibling explicitly, but the 'batch' framing makes the distinction inferable.

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?

Usage is only implied by the word 'batch' versus the singular pencil2d_add_frame sibling; there is no explicit when-to-use, when-not-to-use, or named alternative. The two source modes (list vs directory) are mentioned but not explained as a decision the caller must make.

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