gemini_generate_image

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

Discloses that images are saved to ~/Pictures/gemini/ and full paths are returned. Explains conversation continuation behavior. Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted; description adds meaningful context beyond annotations.

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?

Well-structured with clear sections for modes, args, and returns. Every sentence adds value; no redundancy. Concise yet comprehensive.

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?

Given the tool's complexity (image generation, editing, conversation history) and the presence of an output schema, the description covers all necessary aspects: mode selection, parameter usage, file saving, and return format. An agent can effectively invoke the tool based on 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?

Despite 0% schema description coverage, the description provides detailed explanations for all parameters: prompt (generation vs editing), model (name, default, aspect ratio hint), files (optional paths), and conversation_id (continuation method). Adds significant meaning 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 'Generate or edit images with Gemini' and distinguishes between two modes (without files for new images, with files for editing). It uniquely identifies the tool's purpose among siblings, which are chat/analyze/upload/reset tools.

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 guides when to use without files (new image) and with files (edit/transform). Also provides instructions for using conversation_id to continue refinement, and mentions model defaults. No direct alternatives exist among siblings, so this is sufficient.

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