undo_action

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

With no annotations, the description carries the full burden, yet it discloses nothing about whether the undo is itself reversible, how far back history extends, what happens if no prior action exists, or whether permissions are required. Only the implicit ordering rule ('last action') is conveyed; the rest of the mutation profile is opaque.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity edges toward under-specification rather than tight economy.

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 mutation tool with zero annotations, no output schema, and 0% parameter coverage, the description is too thin: an agent cannot tell what is restored, what happens on failure, or what the second parameter does. It leaves key decision inputs unaddressed.

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%, so the description must compensate. It explains activity_id only by restating it, and the 'project' parameter (defaulting to 'default') is never mentioned, leaving half the parameters undocumented in both schema and prose.

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 names a specific verb (undo) and resource (the last user or agent action), and clarifies the alternative targeting mode via activity_id. It is unambiguous on its own, but it never differentiates itself from siblings such as delete_blueprint or writeback_apply, which is the requirement for a 5.

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?

There is no guidance on when to prefer undo_action over compensating tools like delete_blueprint, nor any prerequisites, scope limits, or failure conditions. The parenthetical hint about activity_id implies an alternative invocation path but doesn't state mutual exclusivity or when to use which.

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