kie_generate

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

With no annotations, the description carries the full burden and excels. It leads with 'SPENDS MONEY,' warns that downloading is ON by default, explains the 14-day retention, and details default output paths. It also explains the noDownload behavior. This is rich behavioral disclosure that goes well beyond basic safety hints.

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 dense but every sentence contributes critical information: the spending warning, core function, prerequisites, safety limit, download default, and skip option. It is front-loaded with the most important warning ('SPENDS MONEY'). Slightly long, but appropriately so for the complexity.

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 the main flow, prerequisites, download behavior, and safety. With 11 parameters and no output schema, it addresses the key invocation concerns. Could mention what the function returns (e.g., task ID or link) explicitly, but this is a minor gap given the rich context and sibling tools handling status/wait.

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?

Although schema coverage is 100%, the description adds meaningful context: it explains the default download path when 'out' is unset, the effect of 'noDownload' (leaves only the link), and the purpose of 'maxCostCredits' as a safety limit. This enriches parameter understanding beyond the raw schema definitions.

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 'Creates a generation task and, with wait=true, waits for the result and downloads the files.' This specifies the verb (creates), the resource (generation task), and additional behavior (waiting, downloading). It also distinguishes itself from siblings by mandating prerequisites like kie_catalog_show and kie_estimate, implying this is the actual generation action.

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?

Explicitly states when to use: 'Before calling: kie_catalog_show (limits) and kie_estimate (price), plus the user's explicit consent to the amount.' It also advises using 'maxCostCredits as a safety limit,' giving clear operational guidance. This goes beyond simple context to include required preconditions and safety measures.

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