linear_unarchiveReleaseStage

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, and the description merely repeats the tool's purpose. It does not disclose behavioral details such as side effects, permissions required, or whether the operation is reversible. The description adds no value beyond the tool name.

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 very concise (three words) and front-loaded with the action and resource. No unnecessary words, but it could be slightly expanded for clarity without losing conciseness.

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 tool with one parameter and no output schema, the description is minimally complete. However, it lacks context about what unarchiving entails (e.g., restoring visibility, effects on related entities). Slightly more detail would improve completeness.

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 covers 100% of parameters with a description for stageId. The tool description does not add any additional meaning or context beyond the schema, so the baseline score of 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 verb (unarchive) and resource (release stage). It distinguishes the tool from siblings in the archive/unarchive family, though it does not explicitly differentiate from similar tools like linear_unarchiveRelease.

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 explicit when-to-use guidance is provided, but the simple action and single parameter make usage intuitive. There is no mention of when not to use this tool or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.