delete_keyframe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete' without mentioning side effects, whether deletion is irreversible, how the index parameter affects which keyframe is removed, or how the tool behaves if no keyframe exists at the given frame. This matches a minimal mutation description that lacks important behavioral context.

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, efficient sentence that front-loads the core action and scope. It avoids filler and redundant phrasing, achieving good conciseness, though it sacrifices detail that other dimensions require.

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?

Despite the presence of an output schema, the tool has four parameters with zero schema-level descriptions and no annotations, and the description explains only the 'frame' aspect. An agent would lack crucial information about how to specify the target object, data path, and keyframe index, making the description incomplete for correct invocation in non-trivial cases.

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 for the undocumented parameters. It adds some meaning to 'frame' as the specific frame where deletion occurs, but it does not explain the required 'object' and 'data_path' parameters or the optional 'index' parameter, which likely disambiguates multiple keyframes at the same frame.

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 clear verb ('Delete') and resource ('a keyframe') with a specific scope ('at a specific frame'), making the primary action obvious. It does not explicitly distinguish itself from siblings like clear_animation or set_keyframe, but the phrasing narrows the operation enough that an agent can infer it targets one keyframe rather than all animation.

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?

There is no guidance about when to use this tool versus alternatives such as clear_animation (delete all keyframes), set_keyframe (create/update), or batch_delete. The description only states what the tool does, not when it should be selected, leaving the agent to infer usage from the tool name alone.

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