game_bone_pose

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'get or set' but fails to mention side effects, such as how setting poses affects animation blending, whether poses reset other properties, or if the tool works in edit mode only. The lack of detail limits transparency.

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 very concise, consisting of a single sentence that gets straight to the point. While it is front-loaded and free of fluff, it could benefit from a slightly more structured format, such as listing the action options. Overall, it is appropriately sized but not maximally informative.

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 the tool's complexity (7 parameters, nested objects, no output schema), the description is too minimal. It does not explain how parameters like action, position, rotation, and scale interact. For a get action, the agent has no information about the return format. The description is incomplete for effective use.

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?

The input schema has 100% coverage with descriptions for all 7 parameters. The tool description does not add any extra meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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's function: getting or setting bone poses on a Skeleton3D node. It uses a specific verb ('get or set') and resource ('bone poses on a Skeleton3D node'), and it distinguishes itself from siblings like 'game_skeleton_ik' which deals with inverse kinematics.

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 versus alternatives, such as 'game_skeleton_ik' or other bone manipulation tools. The description does not specify prerequisites (e.g., node must be a Skeleton3D) or provide context for choosing between get and set actions.

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