execute_operation

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

With no annotations, the description must disclose side effects. It does reveal checkpoint behavior (saves .indd copy to _checkpoints/, requires no target) and frames checkpoint as a safety step before risky edits. However, it does not mention the mutating/destructive nature of other operations, potential error cases, or how skipCheckpoint interacts, leaving a significant transparency gap.

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 sentences with no wasted words. The first sentence front-loads the core purpose; the second adds the most important exception and usage rule. Excellent structure.

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?

With 22 parameters, very low schema coverage, and no output schema, this description is far too brief to be complete. It covers the wrapper concept and checkpoint details but ignores most operation parameters and returns. A complex operation tool needs more context to be reliably invokable.

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 18%, so the description should compensate. It clarifies that checkpoint requires no target and that tag/keep are checkpoint-specific, providing some value. But it does not explain the x/y/dx/dy, find/replace, fill, style, or target resolution options, leaving most parameter semantics undocumented.

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 explicitly labels the tool as a 'thin single-op wrapper around execute_batch' and lists the ten operations it supports. This clearly distinguishes it from the sibling execute_batch tool and specifies its function and scope.

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?

Provides explicit guidance: use for single operations, and 'prefer execute_batch when issuing two or more ops.' It also explains the checkpoint rationale and when to use it, offering clear decision context.

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