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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the conversion action but does not indicate whether the operation has side effects, how the output is returned, whether it is asynchronous, or any limits/errors. This is a significant gap for a tool with no other behavioral metadata.

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 a single sentence that is front-loaded with the action and resource, then adds examples and input source types. Every word contributes value, and there is no redundant or fluff content. It is highly concise and well-structured.

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?

Given the empty input schema, lack of annotations, and no output schema, the description is far from complete. It leaves critical information missing: required parameters, accepted formats beyond examples, how targets are specified, and what the response looks like. While it provides a basic idea of the operation, it is not enough for an agent to call the tool correctly.

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 input schema is empty, so there are no parameter names or types documented. The description mentions 'URL or base64 payload' but does not specify how to pass these values, nor does it mention a target format parameter or output configuration. This provides only a vague hint of the required inputs, insufficient for correct invocation.

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') with a clear resource ('image'), names source types ('URL or base64 payload'), and gives concrete formats (PNG/JPEG/WebP). It is unambiguous and easily distinguished from sibling tools like post_media_video_generate_*, which are about video generation, so the purpose is fully clear.

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 when to use the tool: when an image needs format conversion and is available via URL or base64. However, it does not explicitly mention alternatives, exclusions, or conditions such as size limits or unsupported formats. Usage context is present but not elaborated.

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