generate_image

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

Annotations already indicate readOnlyHint=false, so the description's 'generate' is consistent. It adds the token requirement and usage timing, but does not disclose other behavioral traits like rate limits or effects of missing token, which is acceptable given the simple write action.

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?

The description is two sentences long, front-loaded with the main purpose, and wastes no words on unnecessary details. Every sentence serves a clear function.

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 has 9 parameters, no output schema, and low schema description coverage, the description is too minimal. It does not explain key parameters, return format, or side effects, leaving significant gaps for an agent to correctly invoke the tool.

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 only 11%, with most parameters having defaults but no descriptions. The tool description provides no additional information about parameters (e.g., quality, resolution, aspectRatio), leaving the agent uninformed about their meaning or appropriate values.

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 an AI image' with LemGen, specifying the resource and action. It also provides context about requiring a token and using after user approval, which distinguishes it from siblings like generate_video or enhance_prompt.

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 description includes when to use ('after user approves a final prompt') and a prerequisite ('requires LEMGEN_API_TOKEN'), offering clear context. However, it lacks explicit exclusions or alternatives for when not to use this tool compared to siblings.

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