anim.delete_keyframe

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

Without annotations, the description must carry the burden of behavioral disclosure. It states the destructive nature (delete) but fails to mention error handling (e.g., if keyframe doesn't exist), side effects (e.g., animation curve changes), or default behavior (e.g., current frame, active object).

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 sentence of 10 words, front-loaded with the action verb. It is appropriately brief for a simple delete operation, though could add more context without significant bloat.

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?

Given no output schema, no annotations, and simple operation, the description lacks completeness. Missing usage guidelines and behavioral details make it insufficient for an agent to reliably use the tool in varied contexts.

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 coverage is 0% (no parameter descriptions), so the description should compensate. However, it only mentions 'object property' and 'frame' implicitly, not explaining 'index' or 'object' beyond what schema titles provide. The description adds limited value.

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 the action (delete), the target (keyframe), and the context (on an object property at a frame). It effectively distinguishes from sibling tools like anim.insert_keyframe (insert) and anim.keyframes (list).

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. No mention of prerequisites (e.g., keyframe must exist), error conditions, or relationship to other animation tools like anim.insert_keyframe or anim.keyframes.

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