Apply a plan of operations

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds meaningful context beyond that: the operation is transactional, takes a composite snapshot, and supports rollback. It also notes the dry-run default, though that duplicates the schema default. No contradiction with annotations.

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?

The description is a single, tightly packed sentence with no filler. The most important behavior (transactional atomic apply) is front-loaded, and the dry-run default is a useful trailing note. Every phrase 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 destructive, non-idempotent tool with no output schema, the description leaves too much unspecified: what 'canonical operations' refers to, what the dry-run return looks like, what rollback behavior actually entails, and how errors are surfaced. An agent would need significant external knowledge or schema inspection to invoke this correctly with confidence.

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 only 50%: 'operations' has no top-level description, while 'dry_run' does. The description adds no parameter-level meaning beyond 'canonical operations', which is ambiguous, and it merely restates the dry_run default already in the schema. It does not compensate for the operations parameter being underdocumented.

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 clearly states a specific verb and resource: 'Apply several canonical operations as one transaction.' It also conveys the core value (transactional composite snapshot with rollback) that separates it from one-off mutation tools. However, 'canonical operations' is not defined, and no sibling is explicitly contrasted.

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 transactional and rollback language implies use cases where atomicity matters, and the dry-run default implies a safe preview mode. But there is no explicit when-to-use, when-not-to-use, or alternative routing, leaving the agent to infer when to pick this over individual mutation tools.

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