creator_remove_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. It discloses the basic action but lacks details about consequences (e.g., what happens if no keyframe exists at the current frame), reversibility, or required prerequisites. For a destructive operation, this is insufficient transparency.

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?

Single sentence, front-loaded with the verb 'Remove', and zero wasted words. It communicates the core function efficiently.

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 3 parameters, no required fields, no output schema, and no annotations. The description does not explain how parameters interact (e.g., axis vs. name/uuid) or what happens in edge cases. The 'current frame' context is mentioned but not elaborated. This leaves significant gaps for the agent to invoke the tool correctly.

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 documents all parameters (axis, name, uuid). The description adds no extra meaning about how parameters select the keyframe, such as whether name and uuid are alternatives or both required. Baseline 3 is appropriate given full schema coverage.

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 clearly states a specific action ('Remove a keyframe') on a specific resource ('from the current animation at the current frame'). It distinguishes from siblings like creator_add_keyframe and creator_remove_parameter by specifying the keyframe removal context.

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 implies usage (when you want to remove a keyframe at the current frame) but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention exclusions or alternative tools like creator_add_keyframe or creator_set_parameter.

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