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

Annotations only flag destructiveHint=true; the description goes far beyond by disclosing atomicity ('nothing written' on bad resolutions), that the plan is recomputed server-side, the exact ordered effects (checkpoint, merged tree landing, update-pointer re-stamp, custom-table provisioning, secret fill-in requests), and that adopt mode is undoable via the checkpoint. This is unusually rich behavioral context for a destructive mutation.

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?

Front-loads the imperative action and the resolutions contract before the long ordered effect list, so the callable facts come first. The run-on paragraphs are dense but nearly every clause carries distinct operational meaning; only minor tightening is possible.

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 destructive, multi-effect tool with no output schema and low schema description coverage, the description supplies everything an agent needs: prerequisites, atomicity guarantees, the adopt-mode branch, and the side effects. Nothing material is missing.

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 only 33%, and the description compensates by fully specifying the resolutions shape ({path, contents} with the COMPLETE merged file, or {path, delete:true}) and the adopt flag contract (requires adopt:true with NO resolutions). The agent, hubToken and note params remain undocumented, so it falls short of complete coverage.

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?

States a specific verb+resource ('Apply the update') and immediately ties it to its counterpart 'get_upstream_update', making clear what this tool does and how it differs from the read-only sibling. An agent can distinguish it from flow_get_upstream_status/get_upstream_update without opening any schema.

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?

Explicitly gates invocation on a prior review ('the update reviewed with get_upstream_update') and names the alternative path when the review reported adoptMode: true. It does not spell out when *not* to call it (e.g. no pending upstream update), but the working context is clear.

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