anim_set_keys

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

Annotations already declare readOnlyHint=false and destructiveHint=true, covering the mutation/destructive profile. The description adds efficiency context but does not disclose what happens to existing keyframes on the property, such as whether they are overwritten, merged, or appended.

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?

Bilingual but compact: each version is two sentences with no filler. It front-loads the verb, resource, and key-list format, then adds a concrete walk-cycle usage example that strengthens the purpose without bloating the text.

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?

With 100% schema coverage and annotations carrying the destructive read/write profile, the description is nearly complete for invocation. The main missing context is an explicit statement of overwrite/replacement semantics for existing keyframes, which destructiveHint only hints at.

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 100%, so the schema already fully documents all parameters. The description repeats the keys format ({frame, value}) but adds no new meaning about frame encoding, value types, objects selection, or the relative flag.

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 and resource: 'Write many keyframes for one property in a single call.' It explicitly contrasts with the singular sibling anim_set_key, so an agent can immediately distinguish the bulk operation from the per-key version.

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?

Provides clear when-to-use guidance by naming whole walk cycles as the ideal case and pointing out that it is cheaper than repeated anim_set_key calls. It does not explicitly state the inverse case—use anim_set_key for a single keyframe—but the context strongly implies it.

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