blender_keyframe_delete

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 does not disclose whether the deletion is destructive/non-reversible, whether frame defaults to current frame when omitted, how unspecified keyframe channels are handled, or whether an error occurs if no keyframe exists. A mutation tool with no annotation coverage needs more behavioral disclosure.

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 efficient sentence, no filler. It could be slightly more informative, but it is appropriately sized for a focused deletion action.

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 destructive mutation with no annotations and no output schema, the description is thin. It doesn't clarify defaults (current frame), the meaning of index=-1, or what happens if the target keyframe is missing. An agent selecting this tool among 170+ siblings has little context to invoke it confidently.

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 documents all parameters. The description itself adds no parameter semantics beyond the schema, and the default-frame behavior of the 'frame' parameter is not explicitly explained in the description. Baseline 3 is appropriate because the schema carries the load.

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: 'Delete a keyframe from an object property.' It clearly identifies the operation and target. It does not explicitly differentiate from the sibling blender_keyframe_list or blender_keyframe_insert, but the delete semantics are obvious enough given the name.

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?

No guidance on when to use this tool versus alternatives. For example, there is no mention that keyframe_list should be used to inspect existing keyframes before deletion, or that undo exists as a safety net. The description is a bare statement of function with no context.

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