setup_ik_chain

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

No annotations exist, so the description carries the full burden. It explains the mechanics well (chain follows target, stretch behavior, iteration ranges, return dict) but omits key operational facts: that it creates a constraint on the bone, whether an existing IK constraint is replaced, required mode/prerequisites, and reversibility.

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?

Front-loads purpose in one sentence, follows with practical rigging guidance, then a clean Args list. Every sentence adds information; nothing is redundant with the schema or padding.

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 ten parameters with zero schema documentation and no annotations, the description compensates fully by covering every argument and the core behavior. An output schema exists, so the brief Returns note is sufficient rather than required.

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%, yet the description documents all ten parameters with meaning beyond their titles: chain_count range and the special meaning of 0, pole_angle range plus a concrete common value (-1.571 for a twisted limb), iterations bounds, and the distinction between target_object/target_bone and pole_object/pole_bone.

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?

States a specific verb and resource: 'Give a limb inverse kinematics' with the concrete effect that 'move the target and the chain follows.' This clearly separates it from generic siblings like add_constraint or set_bone_property without opening a schema.

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?

Provides explicit placement guidance ('Put the IK on the last bone of the limb') and explains the conditions for a pole target. It stops short of naming an alternative tool or stating when not to use this, so it falls just shy of a 5.

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