Detect DevOps Center Merge Conflicts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the safety profile. The description adds that it returns work item details and merge conflict records, providing some output context. No side effects are described, but for a read-only check this is acceptable; the additional context earns a 3.

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 two sentences plus a parameter line, with the main action immediately stated. No wasted words; every sentence contributes purpose, usage, or parameter semantics.

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?

Given the tool's simplicity (one required parameter, read-only, no output schema), the description covers what it does, when to use it, and what it returns. Annotations fill the safety gap. No additional detail is necessary for correct invocation.

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% and the parameter description 'DevOps Center work item ID' is identical to the schema's property description. The description repeats this without adding extra meaning (e.g., format, examples, or relationship to other tools), so the baseline of 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?

The description uses a specific verb 'Checks' with a clear resource ('a DevOps Center work item for merge conflicts'). It clearly distinguishes from sibling tools like sf_resolve_devops_merge_conflict (detect vs. resolve) and is not a tautology.

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?

Explicit guidance is provided: 'Use before promoting a work item to identify conflicts that need resolution.' This establishes timing and intent, though it does not explicitly name alternative tools for other scenarios like resolution or checkout.

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