cst_transform_mirror

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

No annotations are provided, so the description must disclose behavioral traits. It mentions mirroring across a plane and an optional center point, but fails to describe the critical copy parameter (whether the original is moved or a copy is created). This omission significantly reduces transparency.

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, direct sentence that front-loads the key operation: 'Mirror a solid across a plane' and mentions the optional center point. No 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 six parameters (including a boolean copy and three center coordinates) and no output schema or annotations, the description is too sparse. It lacks details on copy behavior, coordinate system assumptions, and default center behavior, leaving the agent underinformed.

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 the baseline is 3. The description adds no new information beyond the schema: it repeats plane enum options and the existence of a center point, but does not explain semantics like 'copy' or coordinate defaults.

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 identifies the verb 'mirror' and resource 'solid' across a plane, listing specific plane options (xy, xz, yz) and the optional center point. This differentiates it from sibling transform tools like cst_transform_translate or cst_transform_rotate.

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 guidance on when to use this tool versus alternatives like translate or rotate, nor does it mention prerequisites or exclude negative cases. It only gives a minimal operation statement.

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