ps_resize

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

Annotations declare destructiveHint=false, but the description advertises crop, trim, and flatten, which are destructive document edits (removing pixels/layer data). This is an annotation contradiction. The description also does not disclose undoability or that actions mutate the active document.

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 front-loaded sentence that enumerates the supported actions without filler. Every item earns its place for a multi-action tool.

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 multi-action mutation tool with no output schema, the description covers the action set but leaves out key context: destructive side effects, undo behavior, and active-document requirements. It is adequate but has clear gaps.

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 13%, so the description carries a substantial burden and mostly compensates: it maps width/height to imageSize in px, anchor to canvasSize, bounds order for crop, and angle in degrees for rotate. It mentions 'resample' with no matching schema property and omits some resolution/document semantics, keeping it from a 5.

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 enumerates the Photoshop geometry operations (image size, canvas size, crop, rotate, trim, flatten, flip), making the tool's resource and action set clear. It does not explicitly differentiate from sibling tools like ps_layerOps or ps_selection, so it stops short of a 5.

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 description lists available actions but gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It is implied usage from the action list only.

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