comfyui.asset.upload

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is a write operation. The description adds no additional behavioral context beyond stating it uploads files. It does not disclose potential side effects, authorization requirements, or error scenarios, leaving the agent uninformed.

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 lacks structure or detail. It conveys the core function but omits crucial information about parameters and usage. Could be improved by breaking into clear sections.

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?

With 4 parameters (2 required), an output schema present, and no explicit prerequisites or side effects, the description is incomplete. It does not clarify what 'authorized' means, how server_id and local_path should be specified, or what the asset handle looks like. The output schema may help, but the description itself lacks completeness.

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 0%, so the description must compensate. However, it provides no meanings for server_id, local_path, or original_asset_id. Only the purpose enum is vaguely hinted at by listing file types. This is insufficient for an agent to correctly populate parameters.

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 states 'Upload an authorized local image, mask, audio, or video file to ComfyUI and return an asset handle.' It uses a specific verb (upload) and resource (local files to ComfyUI) and clearly distinguishes from siblings like comfyui.job.get and comfyui.job.cancel, which deal with jobs.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. It only states what the tool does without context for appropriate usage.

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