Revert workspace changes to an entity (🟡 undo)

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

Adds substantial context beyond the annotations: it discloses the two possible outcomes (restore vs. remove), clarifies that removal is scoped to the workspace and that the live container is never touched, and flags dry_run as a preview. That directly supports and explains the destructiveHint=false annotation rather than contradicting it.

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 front-loaded sentence with a parenthetical clarification – no filler, and the most important scoping fact (live container untouched) sits before the dry_run note.

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?

An output schema exists, so return values need no explanation, and the operation's semantics are fully described. The remaining gap is the unresolved workspace_id parameter, which an agent cannot resolve from description or schema.

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 coverage is 0%, so the description must compensate, and it only partially does: it defines the entity_type domain (tag/trigger/variable/folder) and the meaning of dry_run. container, entity_id, and especially the optional workspace_id (default null – which workspace is used?) remain undocumented in both places.

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 ('undo/revert') plus the resource ('this workspace's changes to one tag / trigger / variable / folder'), enumerating the entity types covered. It is clearly distinguishable from the create_*/update_* siblings, which move in the opposite direction.

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?

The description gives concrete usage context: restore a live version's copy, or drop an entity created in the workspace, with dry_run=true as a preview path. It does not name an alternative tool or state when NOT to use it, so it falls just short of a 5.

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