Creates a 3D polygon curve in CST Studio from a name and list of [x, y, z] points, enabling custom 3D geometry paths for simulation models.
Create a 3D polygon curve in CST Studio.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Curve name | |
| points | Yes | List of [x, y, z] coordinate triples |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden of behavioral disclosure. It only says 'Create', implying a write operation, but does not mention side effects, requirements (e.g., open project), or any constraints. The agent cannot infer safety or impact.
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 fluff. It is concise, but the brevity sacrifices completeness.
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 creation tool with no output schema and no annotations, the description is insufficient. It does not explain what a 'polygon curve' is (open/closed), coordinate system units, or whether the tool requires an active project. The agent lacks key context for correct invocation.
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 coverage is 100%, so the schema fully documents the parameters. The description adds no additional meaning beyond the schema, missing an opportunity to explain format, units, or constraints like coordinate system.
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 clearly states the tool creates a 3D polygon curve in CST Studio, specifying the verb and resource. However, it does not distinguish this tool from siblings like cst_create_polygon_extrude or cst_create_analytical_curve, missing an opportunity to clarify when to use this specific tool.
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?
No guidance is provided on when to use this tool vs. alternatives. The description lacks context about prerequisites, typical use cases, or exclusions, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.