Ase Set Frame Duration

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Set a frame's duration,' which implies mutation but does not disclose side effects (e.g., whether the sprite file is overwritten, whether the operation is reversible, or what happens on invalid frame indices). For a mutation tool with zero annotation coverage, this is a significant gap.

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, front-loaded sentence with no waste. It communicates the core action immediately and efficiently.

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?

While the tool is simple (3 scalar parameters), the description is too sparse to be complete. It omits essential context about parameter meaning, range constraints, and behavior. An output schema exists, so return values may be covered, but the lack of parameter semantics makes correct invocation uncertain for an agent.

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 schema has 0% description coverage, and the description adds nothing about the parameters. It doesn't explain that 'frame' is an index (likely zero-based), that 'duration_ms' is an integer in milliseconds, or that 'sprite_path' identifies the target sprite. The agent must infer all semantics from the schema's bare types, which is insufficient.

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 'Set a frame's duration in ms.' states a specific verb (set), a precise resource (frame's duration), and the unit (ms). It clearly distinguishes from sibling ase_set_frame_duration_all by specifying 'a frame' rather than all frames, so an agent can tell them apart without opening schemas.

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?

The description offers no explicit when-to-use guidance or exclusions. It doesn't mention the sibling ase_set_frame_duration_all or any prerequisites, such as the sprite needing to be loaded or the frame index being zero-based. The usage context is only implied by the name.

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