Delete keyframes

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state destructively. The description usefully notes that omitting frames removes ALL animation, disclosing the escalation in destruction scope, but this same fact is already present in the frames schema description, so it adds limited context beyond structured data.

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?

A single sentence with the verb front-loaded and no filler. Both operational modes are conveyed compactly, and nothing extraneous is included.

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 three-parameter destructive mutation, the description covers the purpose and both deletion modes, and the annotations carry the safety profile with no output schema needed. It is largely complete, with only minor gaps such as reversibility/undo behavior left unstated.

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 meaning of attrId, layerId, and frames is fully documented in the schema itself. The description restates the frames-omission semantics without adding new syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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?

Names a specific verb (delete) and resource (keyframes on an attribute) and scopes the two modes: targeted deletion by frame or full-animation removal when frames is omitted. It is clear what the tool does, though it never explicitly contrasts itself with the sibling cavalry_set_keyframes or add-keyframe flows.

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 condition for the two deletion modes is described (frames present vs omitted), which implies when each form applies. However, there is no explicit guidance on when to reach for this versus cavalry_set_keyframes or other animation tools, and no prerequisites or warnings are stated.

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