Clear Pending Merge Conflicts

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

Annotations already mark destructiveHint=true, and the description adds valuable specifics: the stored conflict analysis is discarded, files and branches are untouched, and the workflow can be recreated by rerunning the merge. This gives the agent a precise mental model of the side effects. No contradiction with annotations.

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?

Two tightly written sentences: the first states the action, and the second qualifies scope and recovery. There is no filler, and the most important behavioral distinction 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 simple cancellation tool with no output schema and strong annotations, the description fully covers what happens, what does not happen, and how to undo the state change. No critical information is missing.

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 coverage is 100%; both projectId and response_format have detailed descriptions, including how to obtain projectId and what each response_format value means. The tool description itself adds no parameter-level meaning, but the schema fully carries that burden.

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 verb ('Abort') and resource ('pending merge-conflict workflow'/'session state'), and immediately clarifies that it does not modify files or branches. This makes it clearly distinct from sibling tools like openl_get_merge_conflicts and openl_merge_project_branches.

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 frames when to use this tool: when a pending merge-conflict workflow needs to be aborted, and it notes that rerunning the merge recreates the analysis. It does not explicitly name alternatives or exclusions, but the usage context is unambiguous enough for an agent.

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