bone_local_to_world

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

No annotations are provided, so the description must disclose behaviors. It states a pure computation (combining transforms) with no side effects, destruction, or auth needs. However, it does not clarify whether the operation mutates inputs or the nature of the output. The description is adequate but minimal for a math 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?

A single sentence that precisely describes the operation without any redundant words. Every element is essential, and the structure is front-loaded with the core action.

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?

The description lacks information about the return value (expected to be a world matrix or transform). No output schema exists, and the description does not clarify what the tool outputs. Given the complexity of 3D transforms and the presence of sibling tools with similar purpose, this is a notable gap.

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 50% (only parentWorldMatrix and localRotation have descriptions). The description adds context by naming the three local components (position, rotation, scale) but does not explain the optionality of localScale, the exact output format, or the meaning of the matrix operation. It partially compensates for missing schema details.

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 explicitly states the operation: combining a parent bone world matrix with child local position, rotation, and scale. This clearly distinguishes it from siblings like 'bone_hierarchy_to_world' which processes a hierarchy of bones.

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 implies the tool is used for transforming a child bone's local transform to world space given a parent matrix, but it does not provide explicit guidance on when to use this vs. alternatives like 'bone_hierarchy_to_world' or other matrix tools. No exclusions or prerequisites are mentioned.

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