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

With no annotations, the description carries the full load and does well: it discloses that the restored workflow keeps the same id, starts disabled, gets a new inbound trigger URL, and that the call fails when a referenced pipeline is missing. It omits permission requirements and what the response contains, but the key side effects and failure mode are covered.

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?

Two sentences, front-loaded with the action and its outcome, followed by the failure condition and remedy. Every clause adds information; nothing is padding.

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 single-parameter mutation with no annotations and no output schema, the description covers side effects, the identity guarantee, and the blocking dependency. Only the returned payload and authorization requirements are left unstated.

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?

One parameter at 0% schema description coverage. The description implies workflow_id refers to the deleted workflow's id (and that the snapshot is chosen automatically), which prevents confusion with a snapshot or pipeline id, but it does not state the id format or where to obtain it.

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?

States a specific verb and resource ('Re-create a deleted workflow from its last snapshot') and pins down scope with parenthetical detail about identity and initial state. It implicitly separates itself from workflow_history_restore by specifying the snapshot is the source, but never names a sibling explicitly.

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 clear condition for use (a workflow was deleted and should be brought back from its last snapshot) plus a prerequisite: referenced pipelines must be restored first. It does not mention alternatives such as workflow_history_restore or workflow_deleted_list, so an agent must infer when this beats version restoration.

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