image.edit

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

No annotations are provided, so the description must disclose behavior. It mentions saving results to disk and returning structured metadata, which is more than absent, but it does not disclose whether original files are overwritten, permission requirements, reversibility, or any other side effects beyond saving. This is a moderate level of transparency.

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, front-loaded with the main purpose, and every word contributes to understanding the tool. There is no verbosity or repetition.

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?

Despite having an output schema, the tool has 7 parameters, 2 enum-based, and 2 required. The description does not cover the semantics of these parameters, nor does it mention constraints or usage context. It is too incomplete for a tool of this complexity.

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 explain parameter meanings. It only implicitly refers to prompt and input_image_paths ('Edit one or more local images', 'multimodal input'). No meaning is added for model, output_dir, filename_hint, transparency_mode, or transparency_threshold, leaving most of the 7-parameter schema unexplained.

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 the tool edits one or more local images using Gemini with multimodal input, and specifies outcomes (saves to disk, returns metadata). The verb 'edit' distinguishes it from the sibling 'image.generate'.

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 by the description—use for editing existing local images—but there is no explicit guidance on when to prefer this over alternatives, no prerequisites mentioned (e.g., file existence), and no exclusions or alternative tool references.

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