creo_create_safe_offset_datum_plane_copy

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

The description goes beyond annotations by disclosing two important behavioral traits: the operation refuses overwrite, and it succeeds only when solid volume remains unchanged. It also states that the datum plane is added only in the new copy, which clarifies the original part is not modified.

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?

Two sentences carry the full behavioral description with zero filler. The core action is front-loaded and the safety constraints are presented succinctly.

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?

With no output schema, sparse annotations, and only 20% schema coverage, the description must carry substantial burden. It provides key safety traits but omits parameter mapping and expected_model/copy_name semantics, making it incomplete for reliable invocation.

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 low (20%), and the description adds useful context like 'nonzero offset' and 'named planar datum reference.' However, it does not explain the roles of expected_model, copy_name, plane_name, or reference_plane, leaving the agent to infer which parameter corresponds to the new plane name versus the reference plane.

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 names a specific verb+resource: copy the current Creo part and create one datum plane at a nonzero offset. It also distinguishes itself from sibling safe-copy tools by specifying 'one datum plane' and 'named planar datum reference' rather than a generic copy operation.

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?

It clearly communicates the intended scenario: create a safe copy of the current part while adding exactly one offset datum plane. It does not explicitly list when-not-to-use alternatives, but the narrow scope and safety constraints make the usage context clear.

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