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

Goes well beyond the annotations: declares atomicity, undoability, merge semantics for concurrent edits, the SESSION_CONFLICT failure mode, automatic checkpointing of previous state for significant agent batches, and post-conflict recovery advice. This is exactly the mutation/conflict context the destructiveHint annotation cannot convey.

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?

Every sentence carries a distinct operational fact and the core action is front-loaded in the first clause. Dense, but nothing is redundant and the example path makes the abstract path format concrete.

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, non-idempotent mutation tool with annotations but no output schema, the description covers conflict handling, revision pinning, path format, and checkpointing. It stops short of describing auth requirements (token), what success returns, or other error codes, leaving a small gap an agent may need.

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 description coverage is 0%, so the description must compensate. It explains 'changes' paths well with a concrete array example and explains baseRevision's provenance, plus hints at checkpoint via 'automatically checkpoint the previous state', but token, sessionId, actor, label, and the value/remove fields of each change are entirely unexplained.

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 ('Apply') and resource ('one atomic, undoable batch of changes to the shared preset'), making it clearly distinguishable from read-only siblings. The only slight wobble is calling the target a 'shared preset' while all parameters reference a sessionId/session, which could momentarily confuse an agent.

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?

Gives concrete routing instructions: take baseRevision from read_session, use describe_nodes templates when adding nodes, and never blindly replace the whole document after a conflict. It lacks explicit when-not-to-use guidance (e.g. restore_session for rollback or checkpoint_session for manual snapshots), which keeps it short of a 5.

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