Generate Image(s)

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

Annotations already indicate non-readOnly (write operation) and non-idempotent, but description adds no behavioral context beyond what annotations provide. It does not disclose potential side effects, no mention of auth requirements, rate limits, or what happens with different model choices. Descriptions should add value beyond structured fields.

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 concise—one sentence and a short instruction. No wasted words, but could be restructured to include essential guidance. Concision is high, but at the cost of completeness.

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?

Tool has 10 parameters, complex schema with enums, and no output schema. Description fails to explain return values, supported image formats, error handling, or model-specific constraints. Incomplete for a complex generative 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 coverage is 100%, so baseline is 3. Description provides minor added guidance regarding explicit provider+model but does not add significant meaning beyond what parameter descriptions already cover. Minimal extra value.

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?

Clear verb+resource: 'generate image(s) from a text prompt'. Description states action and input. However, it does not explicitly distinguish from sibling tools like 'edit_image' or 'get_model_capabilities', though the tool name itself is unambiguous.

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?

Provides implicit usage guidance ('Prefer explicit provider+model; respect model capabilities') but lacks explicit when-to-use, when-not-to-use, or alternatives. No mention of why one would choose this tool over 'edit_image' or when to use 'get_model_capabilities' instead.

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