delete_keyframe

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 'delete' without explaining that the operation is permanent, what happens if the keyframe does not exist, or how the 'index' parameter affects deletion (e.g., deleting all keyframes at the frame when index=-1). No side effects or prerequisites are mentioned.

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, concise sentence with no fluff. However, it is so brief that it fails to convey necessary context for a 4-parameter operation. While it is appropriately front-loaded, it sacrifices critical details required for correct invocation.

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?

The tool has 4 parameters, no annotations, and a non-trivial deletion operation. The description is far from complete: it does not explain the role of index, the required object/data_path combination, or the effect on f-curves. An output schema exists but the description should still provide usage context, which it lacks.

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%, so the description must compensate, but it adds no parameter information. The names object, data_path, frame, and index are present in the schema but their roles are not clarified. In particular, 'index' with default -1 is ambiguous—does it mean delete all keyframes at that frame? The description is silent.

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 uses a specific verb 'delete' with a clear resource 'keyframe' and scoping ('at a specific frame'). It is easily distinguished from sibling tools like set_keyframe or clear_animation, which create/modify or remove all keyframes respectively.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that clear_animation exists for removing all keyframes, nor does it explain when one might need to use index to delete multiple keyframes at a frame. The context is entirely absent.

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