comfyui_workflow

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

Annotations already indicate destructiveHint=true, and the description reinforces this by listing 'delete' as an action. Additionally, it adds useful behavioral hints, such as using 'view' before 'modify' to discover node IDs, which provides guidance beyond the annotations.

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 that efficiently conveys the tool's purpose and actions. It is front-loaded and contains no wasted words, making it easy to read.

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 description covers the actions but does not explain return values for each action (e.g., what list returns, success messages). Given no output schema and moderate complexity, the description could be more complete by specifying output types.

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?

The schema descriptions cover all parameters (100% coverage). The description adds value by clarifying that the 'name' parameter defaults to filename in import and that 'nodeId' requires prior view action, enhancing meaning beyond 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 description clearly states the tool manages ComfyUI workflow templates with specific actions (list, view, import, modify, delete). It uses a specific verb 'Manage' and identifies the resource 'ComfyUI workflow templates', distinguishing it from sibling tools like generate_image or enhance_prompt.

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 provides the actions available but does not explicitly state when to use this tool over alternatives. It implies usage for workflow management but lacks exclusions or context for choosing this tool versus others.

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