Select a geometrical set by name to direct all new GSD geometry into it, ensuring organized surface modeling in CATIA.
Choose which geometrical set new GSD geometry goes into.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Geometrical set name. |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare idempotentHint=true and destructiveHint=false. The description adds the stateful effect that future GSD geometry will be placed into the chosen geoset, which is useful. It does not disclose additional behavioral details such as whether the geoset must exist beforehand or what happens if an invalid name is given.
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, front-loaded sentence with no filler. It immediately conveys the purpose and effect of the tool.
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 simple one-parameter state-setting tool, the description is adequate but leaves out the prerequisite that the geoset must exist (managed by catia_gsd_create_geoset). An agent might need that context to avoid errors, but the tool is otherwise well-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%, and the parameter 'name' is documented as 'Geometrical set name.' The tool description adds minimal extra meaning beyond restating that the name identifies the target geoset, so it stays at the baseline of 3.
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 uses a clear verb ('Choose') and a specific resource ('geometrical set') and explains the effect ('new GSD geometry goes into'). It distinguishes this tool from siblings like catia_gsd_create_geoset and catia_set_active_body by making the target resource explicit.
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?
Usage is implied: the agent can infer this is used before creating GSD geometry to route it to a specific geoset. However, there is no explicit mention of when to use it over alternatives such as catia_gsd_create_geoset or catia_set_active_body, nor any prerequisites like 'the geoset must already exist'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.