generate_image

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

Discloses async behavior and returns taskId, which is key for polling. No annotations provided, so description carries burden. Does not mention side effects like delayed file writing, rate limits, or authorization—could be more transparent.

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?

Two sentences, front-loaded with action and async note. No redundant information.

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?

Covers essential: async generation, taskId for polling, and output path. No output schema, but description explains return value. Could clarify that file is saved only after task completes.

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% with descriptions. Description adds no extra meaning beyond schema (e.g., prompt is 'text prompt', outputPath is 'local path'). Baseline 3 for high coverage.

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?

Clearly states action (generate image from text prompt), async nature, and follow-up polling via get_task_status. Distinguishes from siblings (describe_image, generate_video, get_task_status).

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?

Implies usage context: generate then poll via get_task_status. Does not explicitly exclude alternatives like describe_image or generate_video, but the name and description provide sufficient guidance for an agent.

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