Traceback To Node

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

Annotations already indicate the tool is not read-only and not destructive. The description adds useful context about resetting to a validated state, but does not disclose potential side effects (e.g., discarding unvalidated changes, reversibility). This is acceptable but not rich.

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, focused sentence that front-loads the action and condition. It contains no redundant information and is easy to parse.

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 simple rollback tool with no output schema, the description provides sufficient context to understand purpose and usage. With annotations covering safety profile, it is adequately complete, though a note about irreversibility or effect on unvalidated state would make it more robust.

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 100%, so parameters are already well-documented. The description adds contextual meaning around the target node ('prior validated node') but does not provide additional parameter-specific details beyond what the schema offers.

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 states a specific action ('Reset task execution state back to a prior validated node') and a clear trigger ('when downstream test/verification fails'). It also distinguishes itself from similar rollback tools like undo_last or revert_to_timestamp by emphasizing the 'validated node' aspect.

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 clearly indicates when to use the tool: when downstream test/verification fails and you want to roll back to a prior validated node. It does not explicitly mention alternatives or when not to use it, but the 'validated node' constraint provides practical guidance.

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