creo_add_project_component_fixed

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

The description goes well beyond the destructiveHint annotation by explaining what happens: fixed constraint is applied, the assembly is regenerated and saved, and older versions of only that assembly family are recycled. This is exactly the kind of side-effect disclosure that helps an agent understand irreversible behavior, and it does not contradict annotations.

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 dense sentence that front-loads the main purpose and then lists the consequential effects. It is efficient, though slightly long and could benefit from clearer separation between the core action and the 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, mutation-heavy tool with no output schema, the description covers the main operational steps and the key destructive side effect accurately. The main gap is the unclear role of 'expected_component', plus the absence of explicit guidance about when a user would choose this tool over similar add-component tools.

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 0% schema description coverage, the description must compensate. It clarifies 'translation_x/y/z' as XYZ translation values, 'component_model_file' as an existing project part, and 'expected_assembly' as the current expected assembly. However, 'expected_component' is not explained, and the relationship between it and 'component_model_file' remains ambiguous.

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 ('Add an existing project part'), a specific resource ('current expected Creo assembly'), and a distinctive method ('apply a fixed placement constraint'). This clearly differentiates it from sibling tools like mate_align or align_insert_three by emphasizing the fixed placement constraint.

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 operational context: use this tool when adding an existing part at a verified XYZ translation with a fixed placement constraint, followed by regeneration and save. However, it does not explicitly state when NOT to use it or name alternative tools for other constraint types, leaving selection guidance mostly implied.

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