add_frame

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

The description explains that appending is additive and describes the effect of the 'copy_from' parameter. It also states what is returned (new frame number and updated frame count). However, it does not mention persistence or side effects, but given no annotations, this is adequate.

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 concise, using a short paragraph with clear Arggs and Returns sections. Every sentence is informative and there is no redundancy.

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?

All necessary information is covered: purpose, parameters, return values, and parameter behavior. No missing details given the tool's simplicity and lack of output schema.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: 'duration_ms' default, 'copy_from' as 1-based index or null with behavior, and 'filename' required. It adds meaning beyond the schema definition.

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 explicitly states 'Append a new frame to the animation' with a clear verb (append), resource (frame), and context (animation). This distinguishes it from sibling tools like 'remove_frame' and 'duplicate_frame'.

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 explicit guidance on when to use this tool versus alternatives such as 'duplicate_frame' or 'insert_frame'. Usage is implied by the purpose, but no exclusions or preferences are provided.

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