create_image_generation

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of async behavior, cost implications, model selection consequences, or rate limits.

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?

Extremely short but not in a good way; this is under-specification rather than conciseness. There is nothing front-loaded because there is nothing substantive to load.

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?

For a 10-parameter generative tool with no output schema and an async webhook parameter, the definition is completely inadequate. An agent cannot know required inputs, output format, or completion semantics from this description.

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 70%, below the 80% baseline, so the description should compensate for the undocumented parameters (seed, model_id, images items) — but it provides zero parameter meaning. An agent must rely entirely on 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 'Create Image Generation' merely restates the tool name and title verbatim, providing no additional specificity beyond the tautology. It does not clarify scope, distinguish from siblings like create_video_generation or text_to_voice_design, or state what kind of image generation is performed.

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?

There is no guidance whatsoever about when to use this tool versus alternatives. With many sibling creation tools (create_video_generation, sound_generation, generate), the agent receives no routing signal.

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