daz_remove_keyframe

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

No annotations provided; description carries full burden. It explains that other keyframes remain unchanged, and that if no keyframe exists at the frame, `removed=false` (not an error). The return value includes `removed` boolean. It does not explicitly state the destructive nature, but it is implied by 'remove'. Overall good 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?

The description is well-structured with Args, Returns, Example, and Note sections. It is appropriately sized with no redundant information. Every sentence adds value.

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 the output schema existence and the detailed description covering return values, parameter semantics, and edge cases (non-existent keyframe), the description is complete for the agent to use 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 coverage is 0%, so description must compensate. It does so by explaining each parameter in the Args section: `node_label` (display label), `property_name` (label or internal name), `frame` (frame number). This adds valuable meaning beyond the raw schema.

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 tool removes a single keyframe from a property. It distinguishes from the sibling tool `daz_clear_animation` which removes all keyframes. The verb 'Remove' and resource 'keyframe' are specific.

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 explicit when-to-use (remove a single keyframe) and when-to-use-alternative (use `daz_clear_animation` for all keyframes). It includes an example suggesting using with `daz_get_keyframes`. It also notes that removing a non-existent keyframe returns `removed=false` and is not an error.

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