rig.set_bone_transform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Set' implying mutation, but fails to mention necessary conditions (e.g., armature must be in edit mode), side effects (e.g., dependency graph update), error cases (e.g., bone not found), or return value. This is insufficient for an AI agent.

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 sentence, very concise. However, it sacrifices necessary detail for brevity, making it under-specified. It is appropriately front-loaded but lacks completeness.

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?

With four parameters, no annotations, and no output schema, the description is highly incomplete. It omits critical context such as required mode, coordinate system, error handling, and success indicators. An agent would struggle to use this tool correctly without further assumptions.

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 the description must add meaning. It mentions 'head and/or tail position' but does not explain coordinate space, units, or required format of the arrays. The titles in the schema provide similar information, so the description adds negligible value.

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 clearly states the tool sets a bone's head and/or tail position. The verb 'set' and resource 'existing bone's head and/or tail position' are specific. Among sibling tools like rig.add_bone and rig.list_bones, the purpose is distinct, though no explicit differentiation is provided.

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 guidance on when to use this tool vs alternatives (e.g., rig.set_pose_bone) or when not to use it. There is no mention of prerequisites like edit mode, which is typical for bone transform operations. The description lacks any usage context.

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