set_frame_duration_all

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

With no annotations provided, the description must carry the full behavioral burden. It only says 'Set' which implies mutation, but does not disclose whether existing durations are overwritten, whether this is reversible, or what happens to the animation's timeline. No mention of side effects or required permissions.

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 wasted words, but it is under-specified. It lacks structure such as examples, parameter explanations, or conditional notes. It is more of a brief label than a complete tool description.

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 tool with two parameters and no annotations or output schema, the description is too sparse. It does not clarify scope (e.g., which animation or sprite), what 'all' means precisely, or any operational context. It leaves key details ambiguous, making it insufficient for confident invocation.

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 description provides no explanation of the parameters. It mentions 'milliseconds' but does not explicitly map that to the duration_ms parameter or describe the filename parameter. An agent would have to rely solely on parameter names, which are somewhat self-explanatory but not reinforced.

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 states a clear action ('Set') and resource ('all animation frame durations') with units specified. It is specific enough to convey that this tool affects every frame in an animation, though it does not explicitly contrast with the sibling set_frame_duration, leaving the distinction to the word 'all'.

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 on when to use this tool versus alternatives. The sibling set_frame_duration exists, but the description does not mention it or explain that this tool is for batch-setting all frames. No context on prerequisites or intended use cases.

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