Offset Entity

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

Annotations indicate not read-only and not destructive, which is consistent with creating a copy. The description adds that it creates a parallel copy, but does not clarify if the original entity remains or is deleted, nor the default offset direction when side_x/y are omitted. Behavioral context is adequate but incomplete.

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, information-dense sentence that immediately states the core action and resource. Every word serves a purpose, with no redundant or filler content.

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?

Despite having an output schema, the description lacks crucial context: it does not explain default behavior when side point is omitted, nor does it confirm that the original entity remains (copy vs. move). The entity types listed may not be exhaustive given the schema accepts any string handle.

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 coverage is 100%, so baseline is 3. The description adds no new parameter semantics beyond the schema's already clear descriptions for handle, distance, side_x, and side_y. The description does not elaborate on parameter usage or 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 the verb 'Create' and the resource 'parallel copy' along with the specific entity types (line, circle, polyline) and the distance parameter. This distinguishes the tool from siblings like entity_copy or entity_move, which do not offset.

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 does not provide any guidance on when to use this tool versus alternatives such as entity_copy or entity_scale. It lacks explicit when-to-use or when-not-to-use instructions, making it insufficient for an AI to decide between offset and other copy/modify operations.

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