edit_image

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 does not clarify whether the original file is overwritten, what the output of the operation is (e.g., a new file path), or any required permissions. The only behavioral detail is 'optionally using additional reference images', which is minor. This is a significant gap for a mutation tool.

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 primary action, and contains no redundant information. Every word earns its place.

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?

The tool has 4 parameters, no output schema, and no annotations. The description is minimal but not entirely inadequate. It gives a clear when-to-use context and references the main input, but it lacks information about outputs, error handling, or side effects, which are important for a tool that modifies existing files.

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. The description adds some context to imagePath by emphasizing 'specific existing image file', but it largely repeats what the schema already states. It does not add meaningful syntax or format details beyond the schema.

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's function: 'Edit a SPECIFIC existing image file'. This distinguishes it from sibling tools like generate_image, which creates new images, and continue_editing, which implies a different workflow. The mention of 'specific existing image file' and 'exact file path' makes the purpose definite.

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?

Provides a clear usage condition: 'Use this when you have the exact file path of an image to modify.' This gives explicit when-to-use guidance. However, it does not mention when not to use it or name alternative tools directly, so it slightly falls short of the top score.

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