apply_conflict_resolution

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

The description discloses that the operation is 'subject to the same approval policy as any other merge', providing some policy context. However, with no annotations present, there is a lack of detail about potential side effects, reversibility, or what happens if the resolution is out of date. This is mostly an operational note, not full behavioral transparency.

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 concise at two sentences and front-loads the core action ('Apply (merge)...') before the policy note. It is appropriately sized and no wasted words, though it could potentially include more details without becoming verbose.

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?

The tool has a single parameter and no output schema, so the description is relatively complete. It explains the general scope and the approval policy, but it does not clarify what the tool returns or what conditions must be met (e.g., the resolution must be approved) beyond the minimal context. Given the simplicity, it is adequate but leaves some questions.

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%, meaning the schema only provides a bare parameter name with no description. The description adds context that the parameter 'conflict_id' refers to a previously proposed and reviewed resolution, which helps clarify its purpose. Because there is only one parameter and the description gives some meaning beyond just the type, it compensates reasonably for the schema gap.

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 ('Apply') with a specific resource ('previously proposed and reviewed conflict resolution'), clearly indicating this tool merges an approved resolution. However, it does not mention the exact action type (merge) in a way that strongly distinguishes it from other file operations like edit_file or create_file, though the 'conflict resolution' context helps differentiate.

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 implies this tool is for applying a previously reviewed resolution, but it does not explicitly state when to use it versus alternatives like edit_file or get_diff. The phrase 'previously proposed and reviewed' provides some context but no clear exclusion criteria or explicit comparison to sibling tools.

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