set_pose

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

Lacks details on behavioral traits such as whether it overwrites existing pose, merges with current pose, or works outside Pose Mode; no mention of side effects or requirements. Annotations are absent, so the description should carry the burden but falls short.

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?

Efficient docstring with Args/Returns sections; no unnecessary text, well-organized and easy to parse.

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?

Covers basic purpose and parameters, but omits behavioral context (e.g., resets vs blends) and usage scenario. Output schema exists, reducing need to document return values, but overall completeness is merely adequate.

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?

Adds meaning beyond the schema by describing location as 'offset', rotation as 'XYZ Euler in radians', and scale as 'XYZ scale'. This clarifies type and units, though it could specify array ordering or constraints.

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?

Clearly states the verb 'Set' and resource 'pose of a bone in an armature', distinguishing it from other set_* tools like set_location or set_bone_property which operate on different objects or properties.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., set_location for objects, set_bone_property for non-pose attributes), nor any conditions or prerequisites.

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