get_comfyui_workflow

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

No annotations exist, so the description carries the full burden. It does disclose useful behavior: the workflow may be absent ('if any'), the response contains a full graph plus a derived summary, and the API-format graph is optional. It does not say what is returned or raised when no workflow is embedded, nor anything about file access or permissions.

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 sentences, front-loaded with the core action, then the payload shape, then the single optional flag. Every clause carries information and nothing is padded.

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?

An output schema exists, so return-value documentation is unnecessary, and the description covers the main behavioral caveat (missing workflow) plus the optional extra graph. The remaining gap is the mismatch between the stated include_prompt behavior and its schema default of true, which could mislead an agent about default payload size.

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 explains include_prompt reasonably (opt-in API-format graph) but actually conflicts with the schema's default of true, and it only implies that 'path' points at an image file rather than explaining the expected format.

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 (get) and a precise resource (the ComfyUI workflow embedded in an image's PNG text chunks), plus what the payload contains (full UI graph and a summary of node count, models, prompts). No sibling tool in this catalog touches ComfyUI metadata, so differentiation is implicit and unambiguous.

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?

Usage is only implied: an agent can infer this applies to ComfyUI-produced images, and the second sentence gives conditional guidance on when to set include_prompt=true. There is no statement of when not to use it or what happens for images that lack an embedded workflow beyond the parenthetical 'if any'.

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