submit_image_batch

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

Goes well beyond the annotations by disclosing that this is a paid operation, that it is fire-and-return async, that identical (checkpointer, thread_id, task_id) plus parameters reuse records, that parameter conflicts are rejected pre-submission, and that uncertain submissions are never auto-resent. This is rich behavioral context and is consistent with idempotentHint=true.

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?

A single compact paragraph with the core action front-loaded; every clause (async return, dedup key, conflict rejection, no auto-resend) earns its place. Slightly dense/run-on but efficient.

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?

An output schema exists so return values need not be explained, and the description covers the async lifecycle, deduplication and conflict behavior an agent most needs. Remaining gaps are the per-task field semantics rather than anything blocking correct 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?

With schema coverage at 50%, the description adds real meaning by explaining the reuse key formed from checkpointer, thread_id and task_id, and by stating the default concurrency (matching max_concurrency). However it does not describe the per-task fields (task_id, prompt, model, operation) or how tasks are structured, so it only partially compensates.

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?

States a specific verb (submit) and resource (1–10 async paid generation/edit tasks) with scope (batch, concurrency default 3). It implies an async batch distinct from the single-image siblings but never names an alternative, so differentiation is left to inference.

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 async contract ('returns on task IDs, does not wait for image completion') implicitly tells the agent to follow up with wait_image_task/get_image_task, but there is no explicit when-to-use/when-not guidance and no named alternative against submit_image_generation or submit_image_edit.

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