figma_remove_animation

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

No annotations are provided, so the description carries the full burden. It discloses the return shape at a high level ("Returns what's left") and the destructive nature is implicit in "Remove," but it says nothing about reversibility, undo, or what happens when the id/track doesn't exist. Useful but incomplete for a mutation tool with zero annotation coverage.

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?

One sentence plus a short clause, front-loaded with the verb and the mode enumeration, and ending with the return note. Nothing is redundant with the schema.

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 5-param tool with a nested keyframeTrack object and no output schema, the definition covers the selection logic and hints at the response. The fileKey local-vs-cloud behavior is left entirely to the schema, which handles it well, so this is nearly complete.

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 100%, so the baseline is 3; the description earns extra by making the mutual exclusivity of appliedId / keyframeTrack / all explicit, which the schema itself does not state. That is real semantic guidance beyond the field docs.

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 (Remove) and resource (animations from a node) and enumerates the three distinct targeting modes: one applied style, one keyframe track, or all. This distinguishes it from apply/export animation siblings without needing to open their 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 three modes are laid out with the parameter that selects each (appliedId, keyframeTrack, all: true), and it points to figma_get_animations as the source of appliedId. It stops short of naming figma_apply_animation or figma_manage_animation_styles as the inverse/alternative operations.

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