detect_feature_merge_conflicts

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

With no annotations, the description carries the full burden and fails: it never states whether the tool is read-only or mutating, whether it requires auth or a paid tier, or what the result contains. The 'Requires Kiln Pro' line even implies a licensing gate that may not exist for this operation, muddying rather than clarifying behavior.

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?

Only the first sentence earns its place; the following two marketing sentences and the upgrade URL are dead weight that dilute the purpose statement. It is not oversized, but the majority of the text is irrelevant to invoking the tool.

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?

With no annotations, no output schema, and no parameter documentation, the description would need to explain the mutation profile, how to obtain the three version IDs, and roughly what conflicts are reported. None of that is present, and the ad copy displaces the space where it should be.

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?

Three required parameters have 0% schema description coverage and the description gives them no individual treatment. The phrase 'three-way' loosely implies an ancestor/source/target relationship matching the parameter names, but format, valid ID sources, and expected merge base are all undocumented, so the description falls well short of compensating.

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 opening sentence 'Three-way semantic-merge conflict detection for features' gives a specific verb and resource, which is genuinely informative. However, the remaining three sentences are unrelated product marketing about printer calibration, textures, and a paid upgrade that have nothing to do with conflict detection, and the description never distinguishes this tool from siblings like detect_merge_conflicts or detect_decoration_preset_merge_conflicts.

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?

There is no guidance on when to run conflict detection versus the sibling detect_merge_conflicts, nor any prerequisites such as needing the three version IDs to be on a common ancestry. Instead the text pushes a 'Requires Kiln Pro / Upgrade' message that actively misleads an agent about availability rather than helping it choose the tool.

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