set_frame_duration

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only says 'set' a duration; it does not disclose whether the frame must already exist, whether the change overwrites existing timing, what validation or errors occur, or how the operation affects the overall animation. No safety or mutation behavior is conveyed beyond the verb itself.

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 with no padding, and every word earns its place. It is front-loaded with the action and resource, and 'in milliseconds' adds necessary unit specificity without 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?

This is a mutation tool with three required parameters, no annotations, and no output schema, so the description needs to provide substantial context. It omits prerequisites, failure behavior, and the effect of the change on the animation. The description is too thin to safely invoke without relying on external assumptions.

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%, so the description must compensate for missing parameter meaning. It adds useful context for duration_ms ('milliseconds') and hints at frame_index via 'one animation frame', but it never explains filename, indexing semantics, or frame existence requirements. This is insufficient for three required parameters with no schema descriptions.

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 uses a specific verb ('set'), names the resource ('animation frame duration'), and specifies the unit (milliseconds). The word 'one' distinguishes it from the sibling set_frame_duration_all, so an agent can identify what this tool does without opening the schema.

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 when-to-use or alternative guidance is provided. The phrase 'one animation frame' implies single-frame use and contrasts with set_frame_duration_all, but the tool does not state when to choose it over alternatives or mention prerequisites. Usage is implied rather than directly instructed.

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