move_entity

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

No annotations are provided; the description lacks disclosure of behavioral traits such as effects on the entity, coordinate system, or error handling, leaving significant gaps for a mutation operation.

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, precise sentence that communicates the core action and parameter without any extraneous words.

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?

For a simple tool with two parameters, the description is adequate but lacks details on coordinate system, entity availability, or return behavior, leaving some 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?

With 100% schema coverage, the description adds little beyond the schema, merely restating the vector parameter as [x, y, z] without additional context like units or reference frame.

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 uses a specific verb 'Move' and resource 'entity', and specifies the translation vector [x, y, z], clearly distinguishing it from sibling rotation and scaling operations.

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 implies usage for translating entities by a vector but provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools like rotate_entity or scale_entity.

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