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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent already knows this is a non-destructive mutation. The description usefully adds the resulting state (editable and runnable again), but says nothing about idempotency, error behavior when the workflow is not archived, or required permissions.

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?

A single tight sentence with the operation and its outcome front-loaded; every word earns its place. It is perhaps slightly too terse to route between siblings, but there is no filler.

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 two-parameter state-toggle tool with no output schema and annotations covering the safety profile, the description supplies what an agent needs to call it. Only edge-case behavior (already unarchived, missing workflow) is unspecified, which is a modest gap.

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 100%, with both projectId and workflowId fully documented in the schema. The description adds no extra meaning about parameter formats or constraints, so the baseline 3 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 names a specific verb (unarchive) and resource (workflow) and adds the state effect: it becomes editable and runnable again. It does not explicitly distinguish itself from the many sibling unarchive_* tools, but the resource scoping makes the target unambiguous.

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?

Usage is only implied by the phrase 'so it can be edited and run again' — an agent can infer that this is the inverse of archive_workflow, but there is no explicit when-to-use, when-not, or reference to alternatives such as update_workflow or resume_workflow.

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