convert_format

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It meaningfully discloses that transparency is flattened onto white when converting to jpg, which is a significant gotcha. It does not detail output file handling or overwrite behavior, but the disclosed conversion behavior is valuable and directly relevant.

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 two sentences long with no wasted words. It front-loads the core action and formats, then adds the critical jpg transparency caveat as a secondary sentence.

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 simple two-parameter conversion tool, the description covers the essential invocation info: what to convert, what formats are supported, and the key edge-case behavior. An output schema exists to explain return values, so the description does not need to repeat return details. Minor ambiguity about output file location remains, but overall it is sufficient.

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 for the bare schema. It adds meaning by listing valid target formats (png, jpg, webp), but it does not clarify the exact accepted values for image_path or the output behavior. The parameter semantics are partially enriched but not fully documented.

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 uses a specific verb ('Convert'), identifies the resource ('image'), and names the target formats (png, jpg, webp). It clearly distinguishes this tool from sibling tools like resize_image or remove_background by focusing solely on format conversion.

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 the tool is for changing image formats, and the sibling list makes alternatives obvious, but it does not explicitly state when to use this tool versus others. There is no direct guidance about when not to use it, such as 'for resizing, use resize_image'.

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