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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose the mutate-vs-merge behavior and the cloud auto-save behavior in shared edit mode. It does not warn that 'replace' is destructive to the existing graph, nor state validation behavior, reversibility, or return values, which are material gaps for a mutation tool.

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?

Two concise sentences with no filler. The core operation is front-loaded and the auto-save side effect is stated in a single additional clause; every word earns its place.

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 2-parameter tool with no annotations and no output schema, it communicates the essential operation but omits what happens to the previous graph on replace, whether a graph must already exist, and what the tool returns on success or failure. Given the large sibling family, a bit more routing and side-effect context would make it fully complete.

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 input schema already describes both parameters with 100% coverage. The description adds the notion of 'normalized JSON' and frames merge as an alternative to replace, but this is modest extra meaning beyond the schema's existing parameter descriptions.

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?

Clearly identifies a specific operation ('Replace (or merge)') on a specific resource ('the Artifacts graph') using 'normalized JSON'. It is easy to tell apart from export/get/create siblings, though it does not explicitly distinguish itself from roadflow_apply_json.

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 'Replace (or merge)' phrasing describes the two invocation modes and the merge parameter reinforces them, and the auto-save note adds operational context. However, it does not say when this tool is preferable over artifacts_new, artifacts_get, or the roadflow_apply_json sibling, nor does it mention prerequisites or exclusions.

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