Open an existing CST Studio Suite project by file path. In connected mode it loads in the running instance; offline, it stores a reference for later use.
Open an existing CST Studio Suite project. In connected mode the project is opened in the running instance; in offline mode a reference is stored for subsequent operations.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Full file path of the existing .cst project to open. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It explains connected vs offline mode but lacks detail on prerequisites, side effects, or error handling. Beyond schema, it adds mode context but not comprehensive behavior.
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?
Two efficient sentences with zero waste. Front-loaded with verb and resource, concise and structured effectively.
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 open operation, the description is fairly complete. It covers modes and parameter. Missing are return value (no output schema) and edge cases, but acceptable for this tool's simplicity.
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% with a clear description for the only parameter (path). The tool description adds no additional parameter meaning beyond what the schema provides, so baseline 3 is appropriate.
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 opens an existing CST Studio Suite project, distinguishing between connected and offline modes. Among siblings, cst_create_project and cst_close_project highlight the distinct purpose.
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 implies when to use (opening an existing project) and mentions two modes, but does not explicitly note when not to use or reference alternatives like cst_create_project.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.