Copy Entity

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool copies an entity and returns info of the new copy, confirming it is a mutation that does not alter the original. However, it does not elaborate on permissions, side effects, or response format beyond what is implied.

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 consists of two short sentences, each serving a purpose: one for the action and one for the return value. It is front-loaded with the main action and contains zero redundancy.

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 simplicity, full schema coverage, and the presence of an output schema (implied by 'Returns info'), the description is fairly complete. It covers the core operation and return. However, it does not explicitly state that the original entity remains unchanged, which is a minor gap for a copy operation.

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 100%, so the schema already documents each parameter. The description restates the displacement parameters (dx, dy, dz) in the context of copying, but adds no new meaning beyond aggregating them. No additional parameter semantics like units or coordinate system are provided.

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 copies an entity and moves the copy by x, y, z displacements. It uses a specific verb ('Copy') and resource ('entity'), distinguishing it from siblings like entity_move (which moves the original) and entity_create_* (which create new entities from scratch).

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 provides no guidance on when to use this tool versus alternatives such as entity_move or entity_rotate. It does not mention exclusions or prerequisites, leaving the agent to infer context from sibling tool names.

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