Restore an archived release stage to active status by providing its stage ID, enabling continued use in Linear's project workflows.
Unarchive a release stage
| Name | Required | Description | Default |
|---|---|---|---|
| stageId | Yes | The ID of the release stage to unarchive |
| Name | Required | Description | Default |
|---|---|---|---|
| success | No | ||
| releaseStage | No |
Changes observed during successful MCP inspections.
v1.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds no further behavioral context beyond stating it is an unarchive operation. The agent can infer mutation from the action.
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 is appropriately concise for a simple tool.
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's simplicity (single required parameter, no nested objects, output schema exists), the description is largely complete. Could be improved by mentioning the return behavior or side effects, but not essential.
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 stageId. The tool description does not add any additional meaning beyond the schema, meeting the baseline.
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 'Unarchive a release stage' uses a specific verb ('Unarchive') and resource ('release stage'), clearly distinguishing it from sibling tools like linear_archiveReleaseStage.
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 on when to use this tool versus alternatives, such as linear_archiveReleaseStage or linear_getReleaseStages. No prerequisites or context are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.