set_frame_duration_all

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

With no annotations provided, the description must disclose behavioral traits. It states the action but does not mention side effects (e.g., overwriting existing durations, requiring a saved file), permissions, or whether the operation is destructive or reversible.

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 short and front-loaded with the action, followed by parameter details. Every sentence is useful, though the parameter list could be formatted more tersely.

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?

As a mutation tool with no output schema, the description should cover return value, error conditions, and preconditions (e.g., file must exist, must be an Aseprite file). It lacks these, making the tool's behavior incomplete for safe 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?

The description includes parameter descriptions ('Name of the Aseprite file to modify', 'Duration in milliseconds') that add meaning beyond the schema's titles. However, it lacks constraints (e.g., positive integer for duration, file path format) and no further details are provided.

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 clearly states the action ('Set') and the resource ('duration of all frames') with the unit (milliseconds). It implicitly distinguishes from sibling tools like 'set_frame_duration' which targets a single frame, making the scope unambiguous.

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?

There is no guidance on when to use this tool versus alternatives (e.g., set_frame_duration for individual frames). No prerequisites, limitations, or exclusions are mentioned, leaving the agent without decision support.

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