creo_create_project_assembly

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

Annotations already declare destructiveHint=true, so the destructive nature is established, and the description adds meaningful behavioral context by specifying version recycling, default placement, verification, and save/display. No contradiction with annotations is present.

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 information-dense sentence with no filler, but the long chain of clauses makes it slightly harder to parse than necessary. All listed steps contribute value.

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 complex, destructive workflow with no output schema, the description covers the environment, template source, attachment behavior, verification, save/display, and version cleanup. It remains slightly vague about what 'recycle older versions' entails, but the overall process is adequately specified.

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 100%, so the schema documents all three parameters thoroughly. The description adds no parameter-level meaning beyond mentioning 'one existing project part', which only loosely maps to component_model_file; baseline 3 applies.

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?

States a specific, multi-step operation: creating a millimeter Creo assembly in the current working directory from the installed template, adding one existing part with default placement, verifying it, saving/displaying, and recycling old versions. This is specific enough to distinguish from siblings such as creo_create_project_empty_assembly and creo_add_project_component_fixed.

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?

Provides clear context: the live working directory already selected in the current Creo session, the installed assembly template, and one existing project part. It does not explicitly name alternatives or say when not to use the tool, so it falls short of the 5 bar.

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