copy_entity

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

With no annotations, the description carries the full burden. It reveals that handle='selection' copies the GUI selection, implying other handles are entity identifiers, but it does not clarify whether the original is preserved, what the return value is, or any side effects. Important behavioral details are missing.

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 sentence that is front-loaded with the core purpose and includes the special-case behavior without wasted 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?

Given the lack of annotations and schema parameter descriptions, the tool description is the primary source of context. It is too sparse to fully guide an agent on how to construct the handle parameter (beyond 'selection') or what to expect in return, despite the existence of an output schema.

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 dx and dy as an offset and highlights the special handle='selection' case, but it does not specify the format of a regular handle value or the units for dx/dy. Partial compensation only.

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 the tool copies an entity with a dx/dy offset, which is a specific verb+resource. It also distinguishes the handle='selection' special behavior, setting it apart from siblings like offset_entity or move_entity.

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 copying entities and mentions the special 'selection' handle, but it does not explicitly state when to choose this over alternatives like move_entity or offset_entity. No exclusions or alternative tool references are given.

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