creo_reverse_project_sheetmetal_planar_wall_to_positive_z

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

The description goes far beyond the annotations: it discloses dimensional guards, envelope verification with unchanged volume, assembly regeneration, conditional saving only after verification, preservation of assembly-driven dimensions, post-state active part, and version recycling. These are material behavioral traits not available in annotations, and there is no contradiction with destructiveHint=true.

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 one long, dense sentence, but nearly every clause adds meaningful behavior. It is not padded, though readability would improve by splitting into separate sentences for the main action, verification, and side effects.

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 destructive, complex, 10-parameter tool with no output schema, the description covers the workflow and side effects well. However, the lack of parameter-level guidance and failure-behavior details means an agent cannot fully determine what to supply or what happens on verification failure.

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% for 10 required parameters, so the description must compensate, but it only refers generically to thickness, length, width, and a 'named top assembly'. It does not explain expected_assembly, expected_sheetmetal, feature_id, symbols, or how the expected_* values are used, leaving agents guessing at critical invocation inputs.

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 action ('reverse'), a specific resource ('verified first planar-wall thickness direction of the active native Creo sheet-metal project part'), and an exact target state ('from -Z to +Z'). It clearly distinguishes this from sibling tools like creo_reverse_project_skeleton_box_direction.

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 gives a clear usage context: the part must be the active native Creo sheet-metal project part, the first planar wall must already be verified, and the operation applies on FRONT. It does not explicitly list exclusions or name alternative tools when not to use it, so it misses only the highest bar.

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