invokeai_workflows

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

With no annotations provided, the description carries the burden. It discloses the return format, save/update behavior, and that workflow_json must be a full workflow object. It does not mention whether delete is irreversible or how errors are surfaced, but it covers key behavioral aspects adequately.

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 well-structured with clear sections: purpose, rationale, return format, examples, and notes. Each section earns its place without redundancy, and critical information is front-loaded in the opening sentence.

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 is a CRUD manager with moderate complexity, and the description covers it fully: operations, return format, examples, save semantics, and required fields. It clearly differentiates from sibling tools, making it adequately complete for an agent to select and invoke 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 100%, so parameters are already documented. The description adds value beyond the schema by explaining save semantics, requiring a full workflow object, and providing examples that tie parameters to operations. This goes beyond the baseline mid-rating.

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 opens with a specific verb-resource pair: 'Manage InvokeAI node workflows (list, get, save, delete)', which clearly states the tool's scope. It further distinguishes from siblings by noting that running a workflow graph goes through invokeai_generate or enqueue, so this tool is for the stored library.

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 explicitly provides when and when not to use the tool: 'Running a workflow graph goes through invokeai_generate or a raw enqueue - this tool manages the stored workflow library.' It also clarifies save semantics (create vs update) and gives usage examples for each operation, which serves as clear usage guidance.

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