Resize Image — Change image dimensions to any size. Runs in the browser. Covered by signup welcome credits and by the Day Pass (24-hour unlimited on this workspace group). All three credit-based workspaces unlock with the same one-time credit pack — there is no per-workspace subscription. See mioffice.ai/pricing for current plans.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'Runs in the browser' and credit coverage, but fails to disclose how the tool receives the image (e.g., via file picker or currently open file), whether it overwrites or creates a new file, or any side effects. This is a significant gap for a tool with no parameters.
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 core action is front-loaded in 'Resize Image', but the description then spends several sentences on credit packs and pricing details that are tangential to the tool's function. While not overly long, this dilutes the message and adds unnecessary length.
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 empty input schema and no output schema, the description should clarify how the tool is invoked — such as whether it opens an interactive dialog or operates on a pre-selected image. It only says 'Runs in the browser', leaving ambiguity about how dimensions are specified and what the output will be, making it incomplete for reliable agent use.
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?
The tool has zero parameters, so there is no parameter schema to elaborate. The description's 'any size' loosely implies flexibility, but the baseline for zero-parameter tools is 4, as no parameter documentation is needed.
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 clearly states 'Resize Image — Change image dimensions to any size', naming the exact verb and resource. This distinctly separates it from sibling tools like crop or rotate, which have different operations.
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 implies use when resizing images to arbitrary dimensions but does not provide explicit comparisons with alternatives like upscale or crop, nor does it state when not to use this tool. The context is clear but lacks exclusions or pointers to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have overlapping purposes, such as mio_ai_remove_background and mio_ai_remove_background_pro, mio_ai_video_subtitler and mio_video_auto_captions, and mio_ai_enhancer tools targeting similar media. Agents would struggle to pick the correct tool when several appear to do nearly the same thing.
Naming conventions are mixed: most tools use a mio_ prefix with category, but some use action-based names (mio_image_compress), others use format-pair names (mio_image_avif_to_jpg), and a few use a different prefix (mioffice_list_tools, mioffice_pricing_info). The lack of a uniform pattern makes the tool set harder to navigate.
With 134 tools, the server is massively over-scoped. Even for a broad workspace suite, this count exceeds practical limits and creates significant selection overhead for agents. The number is more appropriate for a full product catalog than an MCP tool surface.
The tool set covers a wide range of PDF, image, audio, video, scanner, and AI operations, so most common tasks are represented. However, there are notable gaps for a 'workspace studio,' such as no document creation or spreadsheet editing tools, and the redundancy between overlapping AI tools suggests the surface is not thoughtfully curated.
