frames

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

No annotations are provided, so the description carries the full burden, yet it discloses no behavior beyond action signatures. It never says that 'delete' irreversibly removes frames, whether 'add' inserts relative to an existing frame, whether operations mutate the file on disk, or what the response contains. The only behavioral hint is the presence of a 'copyFrom' argument on add.

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?

It is a single line with zero filler and the action signatures are grouped coherently with pipe separators. However, the terseness crosses into under-specification — braces, '?' markers and bare key names are unexplained notation that costs the reader more effort than the bytes it saves.

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 mutation-capable tool with no annotations, no output schema, and zero schema descriptions, the description leaves out effects, return values, and error conditions. The action-to-parameter mapping is the only thing filled in, which is not enough for an agent to invoke it confidently.

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 even 'path' and 'action' — the two declared properties — are unexplained. The description does add real value by mapping which extra keys belong to which action (count, after, copyFrom, durationMs, frames, name/from/to/direction), but it gives no meaning, types, units, or defaults for any of them (e.g. is durationMs per frame or total?).

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 is a machine-style list of action signatures (add/duration/delete/tag) rather than a statement of what the tool does. There is no verb+resource phrase such as 'manage animation frames of a sprite', so the agent must infer the domain from the tool name and sibling set. It is not a tautology, but it never explicitly states the resource being manipulated.

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 when-to-use guidance, no prerequisites (e.g. does the sprite/tag need to exist?), and no mention of alternatives. The sibling 'animate' plausibly overlaps with frame manipulation and the description does nothing to disambiguate.

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