restore_deleted_workflow_version

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

Discloses the tool's limited scope (only makes row visible/restorable) and that it does not affect current draft. With no annotations, description carries full burden; missing details on side effects or auth, but sufficient for a simple restore.

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 concise sentences, front-loaded with the primary purpose, no redundant 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?

With no output schema and simple parameters, the description provides all essential behavioral context: what it does, how it differs from sibling, and origin of versionId.

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 covers both parameters with descriptions; description adds no additional meaning beyond what schema provides. Baseline 3 for high schema coverage.

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?

Clearly states 'Undo delete_workflow_version' and 'bring a removed version row back into history', with explicit differentiation from restore_workflow_version.

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?

Explicitly states what the tool does not do ('does NOT change the current draft') and contrasts with sibling restore_workflow_version, plus notes no version check needed.

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