comfy_apply_template

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the safety profile. The description adds that it is a convenience alias, which is a useful behavioral note, but nothing about how the template application works (e.g., whether it validates, what happens on invalid template). With annotations present, the bar is lower, and the description adds some value.

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 concise, using three short paragraphs: purpose, alias note, and Args list. It's front-loaded with the main action, and every sentence adds value. No fluff, appropriate length.

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?

The tool has a simple interface (2 params, 1 required) and an output schema (though not detailed here), so the description doesn't need to explain return values. It likely covers the essentials: what it does and the template options. However, it could specify what the output is (e.g., a workflow object) but that's likely in the output schema. With good annotations, this is fairly complete for a convenience wrapper.

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. The description names the 'template' parameter and lists valid values (txt2img, img2img, upscale, inpaint, controlnet), which adds meaning beyond the schema—this is helpful. For 'params', it only says 'Optional parameters to override template defaults', which adds some context but doesn't specify what keys are accepted or any format. Overall, it partially compensates for the lack of schema descriptions.

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 'Apply a workflow template and return the resulting workflow', which clearly indicates a verb and resource. It also notes it's a convenience alias for comfy_build_workflow, which helps distinguish it from that sibling. However, it doesn't explicitly differentiate from other workflow-related tools beyond that.

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 provides a clear context: it's an alias for comfy_build_workflow, so an agent knows it can use this instead of the longer function. However, it does not mention when to prefer this over other workflow building tools or any exclusions, such as cases where comfy_build_workflow would be more appropriate.

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