Stop a RollDev project environment to halt running services and free up resources. Provide the project directory path to safely terminate the environment.
Stop a RollDev project environment
| Name | Required | Description | Default |
|---|---|---|---|
| project_path | Yes | Path to the project directory |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It merely says 'stop' without explaining what stopping entails (e.g., kills processes, preserves state, is reversible). This leaves ambiguity for the agent.
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, concise sentence with no extraneous words. However, it is so minimal that it may not fully serve its purpose; conciseness should not sacrifice essential information.
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?
Given the tool has only one parameter and no output schema, the description could still provide more context about the stopping process or effects. It lacks completeness for an agent to understand the full impact.
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?
The input schema has 100% description coverage (project_path described as 'Path to the project directory'). The description adds no further semantics beyond what the schema already provides, so baseline applies.
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 action ('Stop') and the resource ('a RollDev project environment'). It distinguishes from sibling tools like rolldev_start_project and rolldev_stop_svc by specifying 'project environment' rather than service or other component.
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 on when to use this tool versus alternatives (e.g., stop_svc). It does not specify prerequisites, such as the project being running, or when not to use (e.g., if the project is already stopped).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.