Reconcile Versions

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description adds real value: it warns that conflict resolution can overwrite values and that a confirmation/gating protocol with exact echo is mandatory. That explains the destructive risk concretely rather than just flagging it.

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?

A single dense sentence that front-loads the action and then the safety constraint. Every clause carries information, though the gating jargon ('write gate', 'destructive gate') is compressed to the point of being slightly opaque.

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?

An output schema exists, so return values need not be described, and the destructive/gating behavior is covered. But for a 14-parameter mutation tool with zero schema documentation, the description leaves the semantics of most conflict-handling and post-processing options unexplained, which is a significant gap.

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?

There are 14 parameters at 0% schema description coverage, so the description carries the full burden, yet it only alludes to target_version and edit_versions via the 'echo' requirement. Critical parameters - conflict_resolution, conflict_definition, abort_on_conflicts, with_post, with_delete, acquire_locks - are never explained in either place.

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 names a specific verb ('reconcile') and resource ('versions') and scopes it to an explicit version range, which separates it reasonably from siblings like post_version or change_version. However, it never explains what reconciliation actually accomplishes (merging edits from edit versions into a target version), so the purpose is recognizable but under-specified.

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?

It implies usage conditions by stating it 'always requires an enterprise write gate, destructive gate and exact echo of the target/version list,' which tells the agent about mandatory preconditions. It does not contrast this with alternatives such as post_version or delete_version, so the when-not-to-use guidance is absent.

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