reaffirm_decision

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

Discloses it appends a single 'reaffirmed_at' amendment to .codevira/decisions.jsonl, configurable expiration via env var. No contradictions with annotations (readOnlyHint=false, destructiveHint=false).

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?

Well-structured with key info upfront (action, context, alternatives). Slightly verbose with version string but justified for clarity.

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?

Fully covers single-parameter tool without output schema; explains behavior, side effects, and configuration. No gaps.

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?

Only one parameter (decision_id) with 100% schema coverage; description adds no new semantics beyond schema description. Baseline 3 applies.

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?

Clear action: 'refresh a do_not_revert decision's soft-expire clock'. Includes version context and explicitly distinguishes from siblings (supersede_decision, set_decision_flag).

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?

States when to call (when decision is soft-expired but still load-bearing) and provides explicit alternatives for semantic rewrites or flag flipping.

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