Convert image

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

Annotations only declare the safety profile (not read-only, non-destructive, not idempotent). The description adds genuinely new behavior: processing stays on the machine with nothing uploaded, a new file is always written, existing files are never overwritten, and the response returns path and sizes (valuable since there is no output schema).

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?

Purpose and format enumeration are front-loaded, followed by tightly packed sentences on execution locality, path semantics, write behavior, and return value. No sentence is redundant; each adds a distinct fact.

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 single-file conversion tool with no output schema, the description covers codecs, output formats, path rooting, local execution, non-overwrite behavior, and return values — everything an agent needs to invoke it correctly. The only omission, explicit batch routing, is a usage-guideline matter rather than a completeness gap.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by listing supported input codecs (GIF, TIFF, HEIC/HEIF) that the output-only 'format' enum does not convey, and it reinforces the allowed-root path convention. It does not add syntax for quality or keepMetadata, so it stops short of 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?

States a specific verb (convert) and resource (one local image), and enumerates both accepted input codecs and output formats. The word 'one' implicitly contrasts with the sibling batch_convert, giving the agent enough to tell single-file from batch conversion without opening a schema.

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?

Usage is implied rather than stated: 'one local image' hints at single-file scope, and the local-only/path-root constraints frame when it applies. However, there is no explicit 'use batch_convert for multiple images' routing or any when-not guidance, so the agent must infer the alternative.

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