text_to_image

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions return values (task id, status, output URLs) but does not elaborate on side effects (e.g., costs, rate limits), auth requirements, or whether it's a long-running operation. For a task creation tool, this is minimal.

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 a single sentence, which is concise but at the expense of depth. It front-loads the core purpose, but for a tool with 8 parameters, it is too brief and lacks structure.

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 complexity (8 parameters, no output schema, no annotations), the description is highly incomplete. It does not explain parameter usage, model options, or the task lifecycle. The agent lacks context to correctly configure 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?

With 8 parameters and only 25% schema coverage (only 'wait' and 'model' have descriptions), the description adds no parameter information whatsoever. It does not explain 'aspect_ratio', 'output_quality', 'output_count', 'output_resolution', 'timeout_ms', or 'poll_interval_ms'. The description fails to compensate for low schema 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?

The description clearly states the tool's action ('Create a Seedream task on RunAPI (text to image)') and the resource ('text to image'). It distinguishes from siblings like 'edit_image' (image editing) and 'get_task' (retrieval) by specifying its unique purpose.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or when not to use it. The sibling tools ('edit_image', 'get_task', 'check_pricing') are not referenced in the description.

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