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

Annotations already declare this is a non-destructive, idempotent, non-read-only mutation, so safety is covered. The description's added value is the note that the workflow may have been archived on the dashboard, meaning origin does not matter, but it says nothing about failure behavior for a non-archived id or what state the workflow returns in.

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?

One short sentence with zero filler, and the operation is front-loaded before the provenance condition. Nothing could be removed without losing 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?

For a one-parameter mutation with full schema coverage and annotations covering safety and idempotency, the description supplies the essential precondition and origin context. The only real gap is behavior on an invalid or already-active workflow, which is a minor omission at this complexity level.

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 a single required workflow_id already documented as 'The archived workflow's id.' The description adds no format, source, or constraint detail beyond that, so the schema carries the parameter semantics entirely — the baseline 3.

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?

Uses a specific verb ('Bring back') on a specific resource ('a workflow'), and ties it to the sibling archive_workflow as the inverse operation, so an agent can distinguish it from restore_agent or restore_version by resource type. It stops short of explicitly contrasting with those siblings, but the verb+resource pairing is 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?

Gives a concrete precondition for use: the workflow must have been archived via archive_workflow or the dashboard, which also tells the agent this tool covers dashboard-archived items too. It does not state what to do when the workflow is not archived, nor explicitly rule out restore_version for a different kind of restoration.

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