kie_upload

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait: the public URL 'lives 3 days', which is critical for the agent to know. It does not cover auth requirements, overwrite behavior, or storage limits, but it adds meaningful context beyond the simple verb 'upload'.

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 concise sentence that front-loads the verb 'Upload' and immediately states the target storage, public URL, lifetime, and purpose. Every phrase contributes value, and there is no repetition or wasted words.

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?

For a simple tool with one parameter and no output schema, the description covers the essential aspects: action, result, longevity, and intended use. It lacks details like file size limits or explicit return format, but 'get a public URL' adequately implies the response type.

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?

The only parameter 'path' is fully described in the schema as 'Path to the file', giving 100% schema coverage. The description does not add any additional semantic information about the parameter, so it remains at the baseline score for high 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 'Upload a local file to kie storage and get a public URL', specifying both the action and the outcome. This uniquely distinguishes it from sibling tools like kie_doctor or kie_catalog_list, which serve unrelated purposes.

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 phrase 'Needed for references' provides a clear usage context, indicating when the tool should be used. However, it does not explicitly mention alternatives or when not to use it, so it lacks explicit exclusion criteria.

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