movej

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

With no annotations, the description carries the full burden. It fails to disclose critical behaviors such as whether the movement is blocking or non-blocking, safety requirements, error handling, or side effects like joint limits. The brief parameter list does not cover operational context.

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 relatively concise but lacks structure. It lists parameters in a plain text line-by-line format without proper formatting or grouping. While front-loaded with the purpose, the parameter list is verbose.

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 no output schema, no annotations, and 6 parameters, the description is incomplete. It does not explain return values, error conditions, or prerequisites like robot connectivity or power state. The tool requires more extensive documentation for safe usage.

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?

Despite 0% schema coverage, the description adds meaningful parameter explanations with units (e.g., 'a：加速度（米每平方秒）'). This compensates for the bare schema, though it could be more precise about defaults and 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?

The description clearly states it sends joint angles to a robot, specifying the action as '发送新的关节姿态' (send new joint pose) and the resource as '机器人' (robot). It distinguishes from siblings like 'movel' (linear move) by focusing on joints.

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 like 'movel' or other move functions. The description does not mention prerequisites, constraints, or typical use cases, leaving the agent without context for selection.

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