Creates a new STone solution from a template such as BaseProject or EmptyProject and returns the solution path, so agents can scaffold a project before generating and building ST code.
Create a new STone solution from a template (BaseProject, EmptyProject, ...). Returns the solution path.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| base_dir | No | ||
| template | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the return value ('solution path') but says nothing about permissions, overwrite behavior if the solution already exists, template validity, or side effects.
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 that states the core action and return value with no wasted text. Examples are included compactly.
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 mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It does not explain required versus optional parameters, directory behavior, or creation side effects.
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 0% for all three parameters. The description only partially clarifies the 'template' parameter by naming examples ('BaseProject, EmptyProject, ...'), while 'name' and 'base_dir' remain undocumented.
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 states a specific verb and resource: create a new STone solution from a template. It is clear enough to distinguish this from state/build/file tools, but it does not explicitly compare itself to siblings such as stone_solution_state.
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 provides no guidance about when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the word 'Create'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.