cascadeur_set_pose

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

Annotations already mark the tool as destructive, so the description need not repeat that. It adds meaningful behavioral context: position units, delta rotation degrees, and the important caveat that rig solving can adjust values. This goes beyond the structured annotations.

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, information-dense sentence with no filler. It front-loads the primary purpose and follows with two essential caveats, making every word valuable.

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?

For a tool with three top-level parameters and a nested Transform object, the description omits critical operational details such as what frame and interpolation do, how multiple transforms are applied, and the meaning of reference_frame. The no-output-schema condition further increases the need for explanation, which is missing.

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 0%, so the description must compensate, but it only clarifies units for position and delta rotation. It does not explain frame, transforms structure, interpolation, rotation_quaternion_wxyz, space, or reference_frame, leaving significant gaps.

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 ('Key') and resource ('body or finger controls'), making the tool's function clear. It also implies the action is a pose-setting operation, distinguishing it from sibling tools like get_pose or mirror.

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 gives no guidance on when to use this tool versus alternatives such as cascadeur_set_keys, cascadeur_animate_transforms, or cascadeur_set_properties. There are no explicit conditions, exclusions, or references to sibling tools.

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