edit_images

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

No annotations provided; description shares important constraints (input max 256px, output 32-512px, frame limits by output size) but does not disclose return format, mutability, or whether results are returned directly or as jobs.

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?

Two focused sentences plus a concise constraint table and sibling directive. No wasted words; critical information front-loaded.

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?

With no output schema, description covers constraints and use-case well, but omits what the tool returns (e.g., edited images or job IDs). Still sufficient for selection and basic invocation.

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 high (86%); description adds value by specifying batch range (1-16) and output-size constraints, and explains method enum choices. Still, some parameters like seed lack elaboration beyond 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?

Description clearly states batch-editing 1-16 images consistently, with text or reference image, for animation frames or sprite sets. Specifically distinguishes from sibling 'edit_image' tool.

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?

Explicitly states when to use this tool (for uniform edits on multiple images) and when to use alternative (single image edits use edit_image instead).

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