inflate_workflow

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

No annotations provided, so description carries full burden. It discloses that structure (nodes, types, links, widget values) is preserved while cosmetic fields are not, clearly detailing behavioral traits beyond schema. Minor omission: no mention of error handling or side effects.

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?

Three concise sentences: first describes action, second specifies preservation, third gives post-processing steps. No wasted words, front-loaded.

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 one parameter and an existing output schema, the description covers input, behavior, and next steps adequately. Could mention potential errors from invalid flowzip, but overall complete for the tool's complexity.

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?

With 0% schema description coverage, the description compensates by explaining that 'flowzip' is FlowZip text from get_template. It adds meaning about the parameter's origin and format beyond the schema type string.

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?

Clearly states 'Expand FlowZip text back into a full litegraph workflow JSON' and distinguishes from siblings like get_template (which produces FlowZip) and flowzip_to_api (which converts to API format). Verb 'expand' and resource 'FlowZip to litegraph JSON' are specific.

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?

Explicitly indicates it is the reverse of get_template and that the output must be adapted for submit_workflow, providing context on when to use. Could be more explicit about alternatives, but effectively guides the agent.

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