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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description's 'preserving the authored placement' usefully tells the agent that geometry survives the operation. However, it never states that the current (possibly edited) image content is replaced and unrecoverable, which matters for a destructive, non-idempotent call.

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?

A single front-loaded sentence with no filler; scope and the key preservation guarantee come first.

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 over a deeply nested option object, the description omits return behavior, failure modes when no original is retained, and whether repeated invocations or non-idempotency matter. The one sentence it does have is accurate, but the destructive profile is left largely to the annotations.

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 100%, so the schema carries the parameter burden and baseline 3 applies. The description names elementId and areaId and stresses they must be supplied explicitly, but adds no meaning to areaId's front/back/left/right values or to how they interact with the retained content.

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?

Specific verb+resource: restoring retained original image content, scoped to an element and print area. It is distinguishable from most siblings, but never contrasts itself with the closest relative, restore_background, so the agent must infer which restore applies to which retained content.

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?

No when-to-use, prerequisites, or alternative is given; the only guidance is the adjective 'explicit' before elementId/areaId. Nothing tells the agent when restoration is appropriate versus replace_image or restore_background, nor what happens if the element has no retained original.

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