daz_set_keyframe

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

No annotations provided, so description bears full burden. It discloses behavior: creates or updates keyframes, interpolates automatically, updating existing frame updates value, frames 0-based. Also states return values. Does not mention permissions or potential side effects, but these are minimal for a keyframe tool.

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?

Description is well-structured with sections: purpose, Args, Returns, Example, Note. It is concise yet comprehensive, with every sentence adding value. No redundant or wasted text.

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 4 required parameters, no annotations, but output schema exists, the description covers all necessary aspects: purpose, parameters, return values, examples, and a note about frame range. References a sibling tool (daz_set_frame_range) for completeness.

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 provide parameter meanings. The Args section explains each parameter (node_label, property_name, frame, value) clearly, and examples demonstrate usage with realistic values. This fully compensates for missing schema descriptions.

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?

Description clearly states it sets a keyframe on a property at a specified frame, creates or updates keyframes for animation. Verb is specific ('set a keyframe on a property'), resource is clear, and it distinguishes from sibling tools like daz_set_property (no animation) and daz_remove_keyframe.

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?

Description provides usage context: 'fundamental operation for creating property animations' and advises to use daz_set_frame_range first. It implicitly tells when to use (animation) vs alternative (e.g., daz_set_property for non-animated changes). Explicit when-not-to-use is absent but inferred from examples and notes.

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