Undo Action

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

Annotations already indicate destructiveHint=true, signaling a destructive operation. The description adds context by listing supported undo types but does not elaborate on side effects, irreversibility, or failure modes. Since annotations cover the core trait, a score of 3 is appropriate.

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 consists of two concise sentences: the first states the tool's function and the second provides critical usage guidance. Every word serves a purpose, and key information is front-loaded.

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 tool with two required parameters and no output schema, the description adequately explains how to use it and what it accomplishes. It covers the main necessity (the action_record_uuid) and mentions the broad applicability. A brief note on error scenarios or limitations would improve completeness.

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?

Both parameters have detailed schema descriptions (100% coverage), so the description adds little beyond what is already documented. The instruction to use get_board_activity is repeated from the undoRecordId parameter description, offering no new semantic value.

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 clearly states the tool's purpose: 'Undo a previous action on a board using its action_record_uuid.' It lists specific action types (column changes, deletes, etc.) and differentiates from sibling tools like delete_column by focusing on reversal rather than direct action.

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 provides clear context for use, explaining that it undoes previous actions and instructs how to obtain the required action_record_uuid via get_board_activity with includeData=true. It lacks explicit exclusions or alternatives but overall gives sufficient guidance for appropriate usage.

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