cad_sketch_mirror

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

With no annotations, the description carries the full burden. It discloses that reflected copies are emitted, a MIRROR constraint is added, and the return format. This is good but could mention if original lines are unmodified or any side effects.

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 three sentences with no wasted words. The first sentence defines the action, the second adds constraints and return, and the third sets scope. Perfectly front-loaded and concise.

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 three parameters, no output schema, and no annotations, the description covers the core behavior, constraints, and return value. It lacks parameter details but is otherwise complete for a sketch tool where sessionId is standard.

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%, and the description adds no meaning to the individual parameters 'sessionId', 'entityIds', or 'axis'. It does not explain their format, domain, or purpose beyond the implied axis type.

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 mirrors sketch lines across an existing line entity (the axis), specifies the result (reflected copies and MIRROR constraint), and notes it works on lines only. This distinguishes it from sibling tool cad_mirror which likely mirrors 3D bodies.

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 clear context: mirror sketch lines across a line axis. It notes 'Lines only for now,' implying not for other entities. However, it does not explicitly mention alternatives or when not to use, leaving some ambiguity.

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