Creates a compact preview of an image while retaining the original aspect ratio, reducing file size for faster loading and convenient sharing.
Create a small preview version of an image (aspect ratio preserved).
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Max dimension in px. Default 320. | |
| image_path | Yes | Local path to the image |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that aspect ratio is preserved, a useful behavioral detail not in the schema. However, it does not mention output location, file format, or whether it overwrites, which is a gap for a tool that creates a new artifact.
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 concise sentence that front-loads the action and adds one key behavioral detail. No wasted words.
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?
The tool is simple (2 params, no output schema), but the description does not explain what happens after execution—where the thumbnail is saved, what format, or how the agent should use the result. This is incomplete for a tool that produces a file, especially without any output schema to clarify the return value.
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 100%, so the schema already documents both parameters. The description adds no additional parameter-specific meaning; it only restates that the output is a small preview, which is implicit in the tool name. Baseline 3 applies.
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?
States a specific verb and resource ('create a small preview version of an image') and notes aspect ratio preservation, which clearly differentiates it from siblings like resize_image or convert_format. The purpose is immediately obvious.
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 guidance is provided on when to use this tool versus alternatives such as resize_image. The description only states what it does, not when it should be selected, leaving the agent without routing information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.