lingie_upload_file

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

With no annotations, the description carries the full burden. It discloses the core effect (uploading to ComfyUI input directory) and the return value (filename), which is critical for downstream use. However, it does not disclose edge behaviors like overwrite policy, file-type validation, size limits, or whether directories are created.

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?

Two concise sentences with no filler. The action is stated immediately, followed by the practical downstream guidance about using the returned filename. Every sentence earns its place.

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 low-complexity tool with 2 params and no output schema, the description adequately covers the essential context: what is uploaded, where, and how the result is consumed. It does not promise optional behavior or leave critical return information unexplained. A small gap is the lack of mention of potential failures or prerequisites like ComfyUI availability.

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 description coverage is 100%, so the schema already documents both file_path and filename. The description adds mild value by restricting file types to images/video/audio, which is not present in the schema, but it does not otherwise enrich the parameter meanings.

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 names a specific verb (上传/upload), a precise resource (local files to ComfyUI input directory), and states the intended use cases (image-to-image, reference image, first frame). It is clearly distinguishable from all siblings, none of which perform file upload.

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 explains when this tool is appropriate: before invoking workflows that require local media as input, such as image-to-image or reference-image params. It does not need to state alternatives because no sibling handles upload, though it could have been more explicit about the order of operations relative to lingie_run_workflow.

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