creo_create_project_sheetmetal_flat_walls_batch

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

Annotations only mark the tool as destructive, but the description discloses a full behavioral profile: directory switching, edge ID and length verification, feature-type checks, radius rule, regeneration and volume checks, a single save, limited version recycling, and deletion of the whole batch feature on failure. This far exceeds the annotation hints and gives an agent a clear picture of the operation's 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 dense but every sentence carries operationally useful information. The core action and constraint are front-loaded, followed by a compact list of validations and side effects with no filler or repetition.

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?

The description covers prerequisites, verification steps, atomicity, save behavior, version cleanup, and failure handling, which is substantial for a destructive batch tool with no output schema. It does not describe the success return value, but that is not essential for an agent to invoke the tool correctly.

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 zero schema-described parameters, the description compensates by explaining shared angle and height, edge IDs and expected lengths for verification, and the bend-radius rule. However, expected_model and feature_name are not explicitly explained, though their property names and constraints make their likely roles reasonably clear.

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 and resource: creating 'one native Creo sheet-metal flat-wall feature' on 'exactly two verified straight boundary edges' in one connection and transaction. It clearly differs from the many sibling create-copy and sheet-metal tools because it scopes to exactly two edges in a batch 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?

The description effectively states the preconditions and scope: exactly two verified straight boundary edges, a single connection/transaction, and shared angle and height. It implies when the batch tool is appropriate, but it does not explicitly name the singular flat-wall sibling or state when an agent should prefer an alternative.

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