comfyui_generate_asset

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

With no annotations, the description carries the full burden, and it delivers: it discloses size rounding to multiples of 16, default sizing from the first image, transparent inputs being flattened onto white, trim defaulting to on, upscale toggling extra output, output labels, and checkerboard previews. This is far more behavioral transparency than annotations alone would provide.

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 earns its place, and the core purpose is front-loaded. The level of detail is justified by 13 parameters and zero schema descriptions, with no filler or repetition.

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 13-parameter tool with no output schema and no annotations, the description is unusually complete: it explains the workflow, image-reference syntax, resize behavior, output labels, and extra overrides. It falls just short of full completeness because wait/timeout/seed semantics and the return structure are left implicit.

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. It adds meaningful semantics for prompt, images, width, height, transparent, upscale, trim, extra, and workflow. However, seed, wait, preview, and timeout receive little or no explicit explanation, leaving minor gaps.

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 first sentence names a specific verb ('generate or edit'), a specific resource type ('single asset': object, sprite, icon, character cut-out), and the exact output ('PNG with transparent background'). This strongly differentiates it from the sibling generate_image/generate_video/generate_audio tools even though no sibling is named.

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?

It clearly states when to use the tool: for generating or editing an asset with transparency via the default 'asset' workflow. It gives clear context (single asset, subject-only prompts, image references) but does not explicitly mention when to choose e.g. comfyui_generate_image or comfyui_upscale instead.

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