open_conflicts

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

With no annotations, the description carries the burden of disclosing behavioral traits. It discloses that the tool is advisory and non-resolving, and that it focuses on unresolved import conflicts. This provides meaningful behavioral context beyond the tool's name, though it doesn't detail what 'open' returns or imply read-only status explicitly.

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 sentence that front-loads the verb and resource, and conveys purpose, scope, and advisory nature with minimal words. Every word contributes value; no fluff or redundancy.

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 zero-parameter tool with no output schema, the description is complete. It tells what the tool does (opens unresolved conflicts), why (to reconcile), and a key constraint (advisory; resolve via CLI). This is sufficient for an agent to decide when and how to invoke it.

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?

The tool has zero parameters, so there are no parameter semantics to explain. Per the baseline for zero-parameter tools, the description does not need to compensate for missing schema information, and it doesn't.

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 function: 'Open (unresolved) import conflicts to reconcile.' It uses a specific verb ('open') and resource ('import conflicts'), and adds the qualifier 'unresolved' to define scope. This distinguishes it from sibling tools, none of which handle conflict opening.

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 usage context by noting the action is 'advisory' and that resolution happens 'via the CLI,' effectively telling agents when not to rely on this tool for actual conflict resolution. However, it does not explicitly name alternative sibling tools or state a direct 'when to use' scenario, so it earns a 4 rather than a 5.

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