autocad_mirror_entity

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

Annotations already mark it as non-read-only, non-destructive, and non-idempotent. The description adds the important behavioral fact that the original entity is left unchanged and gives the return JSON shape, though it omits error conditions and document prerequisites.

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 purpose and key invariant are front-loaded in the first two sentences, followed by a compact Args/Returns block. Every section supports correct invocation without filler.

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 creation tool with nested point inputs and an existing output schema, the definition supplies purpose, input meaning, and output shape adequately. It falls just short of 5 by omitting edge-case or error behavior.

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 schema description coverage reported at 0%, the description carries the load and documents all three nested inputs: handle, p1, and p2. It also adds a useful semantic constraint absent from the schema by calling for 'two distinct points' defining the mirror line.

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?

States a specific verb and resource: 'mirror' an 'entity' across a line. The added detail that it creates a copy and leaves the original unchanged helps distinguish it from plain copy or move operations, but no sibling tool is named explicitly.

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?

Provides no explicit when-to-use or when-not-to-use guidance and names no alternatives. An agent must infer its role among transformation siblings like autocad_copy_entity and autocad_move_entity without help.

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