rollback_action

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a snapshot is restored, implying a state mutation, but does not disclose side effects (e.g., whether current changes are lost), reversibility, permissions, or idempotency. This is a significant gap for a rollback operation.

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?

The description is a single sentence, concise and free of fluff, but it is under-specified for a tool with two parameters and no other documentation. It is compact yet not appropriately sized because it omits critical 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?

Given the tool's moderate complexity, the description is incomplete. It lacks parameter semantics, usage guidance, and behavioral context. While an output schema exists, it does not compensate for the missing descriptions needed to select and invoke the tool correctly.

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 0% and the description does not mention workflowId or principalId at all. The agent has no indication what these parameters mean or how they relate to the rollback, making it impossible to invoke the tool with confidence.

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 uses a specific verb ('restore') with a clear resource ('the snapshot before the last approved state-changing action'), which distinguishes it from sibling tools like execute_action or simulate_resolution. The phrase 'before the last approved state-changing action' provides precise scope for what is rolled back.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., must have an approved action), exclusion criteria, or comparison with siblings like plan_next_actions or reset_demo. The agent is left to infer usage solely from the purpose statement.

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