image_convert

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

Adds details beyond annotations: rotation in 90° steps, max_dim bounding long edge, and input collision refusal. Annotations already indicate idempotent and non-destructive; no contradiction.

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?

Two sentences, front-loaded with primary purpose, no extraneous words. Every sentence adds essential information.

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?

Covers main operations and key constraints, but lacks explanation for quality parameter and default behavior when max_dim is null. No output schema to compensate.

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?

With 0% schema coverage, description partially explains path, out_path (format via suffix), max_dim, and rotate_deg, but omits quality parameter. Adds value but not complete.

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?

Description clearly states 'Convert/resize/rotate an image into a NEW file' with format determined by out_path suffix, distinguishing it from sibling tools like image_crop or image_annotate.

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?

Some guidance is given (refuses out_path collision with input), but no explicit when-to-use or when-not-to-use context compared to alternatives like image_crop or ocr_image.

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