move_3d

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

With no annotations, the description carries the full burden for behavioral disclosure. It adds useful context about handle='selection' and the 3D scope, but it omits side effects, standard handle value semantics, and return behavior. This leaves some operational uncertainty, though core behavior is clear.

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?

Two sentences deliver the operation, parameter semantics, and a sibling comparison with no redundancy. The core specification is front-loaded, and every clause contributes value.

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 purpose, parameter meanings, and an alternative tool, which is solid for a 4-param move operation. It doesn't explain full handle syntax or error handling, but the presence of an output schema may cover return details. Overall, the essentials for correct usage are present.

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?

Since schema description coverage is 0%, the description must explain parameters on its own. It interprets dx, dy, dz as the displacement vector and provides one concrete handle meaning ('selection'), but the general handle format is not explicitly defined. This adds significant meaning beyond the bare schema.

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 uses a specific verb 'move' with resource 'entity' and explicitly defines 3D displacement via (dx,dy,dz). It also distinguishes from sibling move_entity, which only shifts in the XY plane, making the purpose unambiguous.

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 phrase 'move_entity only shifts in the XY plane' provides explicit comparative guidance, indicating that move_3d is the appropriate choice for translations involving the Z-axis. This clearly steers an agent toward this tool when a 3D move is needed.

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