set_joint_positions

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals units, the need to step simulation manually, and that omitting joint_indices sets all joints. It does not explain command_id or idempotency_key behavior, but the core behavioral context is well covered.

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 well structured: short intro, units, prerequisites, and an Args section. Every sentence adds value—no filler or repetition. It is appropriately sized for a tool with this many parameters and workflow constraints.

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 covers prerequisites, units, required parameters, optional parameters, and the correct post-call procedure. It omits explanation of command_id and idempotency_key, and does not describe return values, though an output schema exists. Given the complexity of robot control, this is very close to complete but has a few minor gaps.

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%, so the description must compensate. It explains prim_path, joint_positions, and joint_indices (including the default behavior), but fails to document command_id and idempotency_key, which appear in the schema without descriptions. Partial but not complete parameter coverage.

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 states a specific verb ('Set'), a specific resource ('target joint positions on a robot'), and the mechanism ('via ArticulationAction'). This clearly distinguishes it from siblings like get_joint_positions, set_joint_command, and set_joint_drive_config.

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 gives explicit workflow guidance: call get_robot_info first to discover joint names/types/limits, then step_simulation after setting, and explicitly warns not to use play_simulation + sleep. This tells the agent exactly when and how to use the tool versus alternatives.

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