Remove Keyframe

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

Annotations already flag this as a destructive, non-idempotent mutation, so the bar is lower. The description adds genuinely useful behavior beyond them: the read-back of remaining keys and the precise refusal rule ('changing nothing' when no key is within 0.01s), which tells the agent the call can silently no-op.

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?

Two tight sentences, front-loading the action and then the failure/refusal condition. Every clause carries information; nothing is padded or redundant.

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?

With an output schema present, the description need not explain return values, and it still notes the read-back behavior. It covers the mutation, its side effect, and the tolerance edge case; only the relationship to remove_keyframe_range is left unaddressed.

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 fully documents node_id, effect_name, property_name, and time_seconds. The description's phrase 'at a time from an effect property' loosely echoes those params but adds no format or semantics beyond what the schema already supplies; baseline 3 applies.

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 states a specific verb (remove), resource (keyframe), and locus (an effect property at a given time), which is concrete enough for an agent to understand the operation. It does not, however, distinguish itself from the sibling remove_keyframe_range, which an agent must infer from the singular 'the keyframe at a time'.

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?

Usage is implied by the operation itself, and the no-op tolerance is stated, but no alternatives are named. There is no guidance on choosing this tool over remove_keyframe_range for a span of keys, which is the most likely sibling confusion given the sibling list.

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