generate_image_tool

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

With no annotations the description carries the full burden, but it does disclose the important async pattern ('Returns a job_handle to poll'), telling the agent the result is deferred and must be polled via get_status_tool. It omits cost/credit implications, auth requirements, and failure behavior for a 12-parameter generation call.

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 tight, front-loaded sentences with no filler. It is efficient, though its brevity is arguably under-specification rather than disciplined conciseness given the tool's complexity.

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 are partly covered, but for a 12-parameter generation tool with no annotations and 0% param coverage the description is far too thin. It should at minimum explain the model/soul/image input modes and the async polling workflow.

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% across 12 parameters (seed, quality, soul_id, soul_strength, enhance_prompt, input_image_urls, etc.), and the description adds zero parameter meaning. The agent has no guidance on model_id format, soul vs input-image modes, or how optional fields interact.

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+resource ('Submit an image-generation request'), which distinguishes it from the video/speech generation siblings at a high level. However, it never explicitly differentiates itself from the many other generate_* tools (generate_video_tool, generate_batch_tool) beyond the resource noun.

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?

No when-to-use guidance, no prerequisites, and no mention of related siblings like preflight_check_tool, validate_params_tool, recommend_model_tool, or list_models_tool that clearly gate this call. The agent must infer the entire usage context.

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