set_all_frame_durations

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

Annotations (readOnlyHint=false, openWorldHint=false) already tell the agent this is a local mutation, so the bar is lower. The description adds the semantic rationale ('uniform animation speed'), but omits that it overwrites all existing per-frame delays and does not say whether the change is persisted to disk or only to the in-memory sprite.

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 the scope, unit, and intended effect, and no filler. Nothing can be trimmed without losing information.

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 two-param mutation tool with no output schema this is minimally sufficient, but the filename argument is undocumented, the overwrite semantics are unstated, and the relationship to the single-frame sibling is left implicit.

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 coverage is 0% and the schema only types duration_ms as an integer, so the description's disclosure of the millisecond unit is genuinely additive. The required 'filename' parameter, however, has no explanation in either the schema or the description, leaving the compensation incomplete.

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?

States a specific verb (set) and resource (every frame's duration) with an explicit scope qualifier ('every frame') that implicitly distinguishes it from the sibling set_frame_duration. However, it never names that sibling, so the differentiation relies on the agent noticing the singular/plural contrast on its own.

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: the 'every frame' wording suggests bulk application versus the single-frame variant, but there is no explicit guidance on when to prefer this over set_frame_duration or whether it belongs to a specific animation workflow.

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