kie_create_task

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

With no annotations, the description carries full burden. It covers model selection, environment variable fallback, and automatic upload of local image paths. However, it omits that task creation is likely asynchronous and taskId is for polling, nor mentions any side effects, rate limits, or auth requirements.

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?

Three short, front-loaded sentences in Japanese. First sentence states purpose, second explains model switching, third clarifies image_input behavior. No redundant information; every sentence adds value.

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?

The description covers creation and model behavior but is missing critical context about asynchronous execution (taskId used for polling), error handling, and output format. Given the existence of kie_check_task, this omission is notable. The description is adequate but not fully 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?

All 6 parameters have schema descriptions (100% coverage). The tool description adds extra value: explains model default logic based on image_input, and that image_input accepts URLs or local paths with auto-upload. This goes beyond the 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 action ('create image generation task') and immediate return of taskId. It explains model switching logic. However, it does not explicitly differentiate from the sibling tool 'kie_create_tasks' (plural) which likely creates multiple tasks.

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?

No guidance on when to use this tool versus alternatives (e.g., kie_create_tasks for batch operations, kie_check_task for status). The description only states what the tool does, not usage context or prerequisites.

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