create_text_to_image_task

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

With no annotations, the description carries the full burden; it does disclose real behavioral facts (mutual exclusion between generate_multi_view and aspect_ratio, and that remove_background yields a transparent RGBA PNG). It is silent on whether the call is asynchronous, whether it returns a task ID, credit cost, and whether failures are retryable — significant omissions for a creation endpoint.

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?

Front-loaded with the core action, then dense per-parameter constraints with no filler or repeated information. Every clause adds a fact an agent would otherwise have to guess.

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?

Parameter-level coverage is excellent, and with no output schema the RGBA PNG note usefully hints at the return. But a create_*_task tool in a suite full of retrieve/stream/list siblings should tell the agent how to obtain the result, which it does not.

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 0% and all six parameters are undocumented in the schema, so the description does the heavy lifting well: it enumerates ai_model values, gives per-model aspect_ratio valid sets with a default, lists pose_mode values, and explains the two booleans' effects. Only `prompt` is left uncharacterized, which keeps it short of a 5.

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?

States a specific verb and resource: "Generate an image from a text prompt." The phrase "from a text prompt" implicitly separates it from create_image_to_image_task, but it never names that sibling or any other alternative, so the differentiation is inferred rather than stated.

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 says nothing about when to pick this over create_image_to_image_task, nor about the task lifecycle implied by the name — the many retrieve_/list_/stream_/delete_ siblings suggest an async job that must be polled, yet no guidance is given on that workflow.

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