resize_image

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action and scope, but does not reveal whether the operation is destructive, whether it modifies the image in place, whether aspect ratio is preserved, or what the return value is. This leaves significant behavioral ambiguity for such a mutation tool.

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, concise sentence that immediately states the purpose. Every word earns its place, and the structure is front-loaded with the action. There is no fluff or redundancy.

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?

Despite the tool's simplicity, the description is incomplete. It lacks usage guidance, behavioral traits like destructiveness or in-place modification, and parameter clarity. Since there are no annotations, the agent is given too little context to confidently select and invoke the tool.

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 adds only a general notion of 'dimensions' for width and height, but does not explain the image_id parameter or specify units. The schema itself provides only basic titles, so the match is minimal.

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 'Scale the image and its layers to exact dimensions' clearly identifies the verb (scale), the resource (image and its layers), and the specific scope (exact dimensions). This distinguishes it from the sibling tool resize_canvas, which only resizes the canvas, and from other image transforms.

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 provides no guidance on when to use this tool versus alternatives. It does not mention resize_canvas or other sibling tools, and lacks any exclusions or prerequisites. Usage context is entirely absent.

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