generate_image

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

No annotations provided, so description carries full burden. Discloses multi-provider support, default model behavior, size constraints, and URL expiration. Does not mention rate limits or authorization, but covers main behavioral traits.

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 bullet points and sections. Information is valuable but slightly lengthy; some repetition could be trimmed. Good front-loading of purpose.

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 output schema exists, return values need no explanation. Covers generation behavior, provider options, parameter defaults, and URL expiry. Could explicitly mention sibling tool for model list, but overall very complete.

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 coverage signal, description explains 'model' (defaults per provider, custom) and 'size' (recommended dimensions) in detail. 'n' is implied but not explicitly explained; 'prompt' is clarified as text description. Adds significant meaning beyond 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 the tool generates images from text descriptions, using verb 'generate' and resource 'image(s)'. It distinguishes itself from the sibling tool 'list_image_models' by being about generation, not listing.

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 specific use cases (illustrations, posters, etc.), default models per provider, and size recommendations. Lacks explicit 'when not to use' or direct alternatives, but the sibling tool context helps.

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