Remove the Stitch project association from the current workspace or folder, resetting it for a different project. Use this to detach the active folder from its linked Stitch project.
Removes the Stitch project association from the current workspace/folder.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently states that the operation removes an association rather than deleting the project, which is useful nuance. However, it does not disclose whether the action is reversible, whether it affects other workspace state, or whether confirmation is needed.
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 wasted words. It immediately conveys the verb, target, and scope, which is ideal for a tool of this simplicity.
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 zero-parameter tool with no output schema and no annotations, the description is largely complete: it names the action and the exact thing being removed. A short note on reversibility or side effects would improve completeness, but given the low complexity, the current description is adequate.
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 tool has zero parameters, so the baseline for this dimension is 4. The description adds meaningful implicit context by identifying the current workspace/folder as the operation target, which is the only relevant input. No parameter-level clarification is needed.
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 action ('removes') and a specific target ('Stitch project association from the current workspace/folder'), which is clear and scoped. It does not explicitly name or differentiate from sibling tools like delete_project or set_workspace_project, but the word 'association' signals it is not deleting the project itself.
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 clearly implies when to use the tool: when the current workspace/folder has a Stitch project association that should be removed. It does not mention alternatives or exclusions, but the scope ('current workspace/folder') gives enough context for an agent to distinguish it from project-level operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.