comfy_insert_blueprint

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

Annotations already provide a strong safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds useful behavior beyond that: it reveals that `inputs` are per-node overrides 'applied to the blueprint's nodes when inserted,' and that the result is a workflow dict. No contradiction with annotations exists.

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 short and front-loaded: one clear action sentence followed by two compact argument notes. Every sentence earns its place, with no filler.

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?

Given two simple parameters, strong annotations, and an existing output schema, the description covers the remaining uncertain pieces: where `name` comes from, how `inputs` interact with nodes, and what is returned. Nothing critically missing for an agent to invoke this tool correctly.

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 carry parameter meaning. It does: `name` is a blueprint name from `comfy_list_blueprints`, and `inputs` is an optional `{node_id: {input_name: value}}` override map. It lacks examples or defaults, but these are present in the schema.

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 opening statement 'Materialize a blueprint into a workflow dict' gives a specific verb and resource, and immediately distinguishes it from `comfy_list_blueprints` and other workflow composition tools. It even points to the source of the `name` argument ('from comfy_list_blueprints'), which removes ambiguity.

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 clearly establishes where the tool fits: take a blueprint name produced by `comfy_list_blueprints` and produce a workflow dict. It gives enough context for correct use, but it does not explicitly call out when not to use it or name alternatives such as `comfy_apply_template`, so it stops short of 5.

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