comfy_export_workflow

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows this is a safe, non-mutating operation. The description adds minor context (returns 'formatted nicely as JSON'), but it does not disclose any additional behavioral traits (e.g., size limits, formatting specifics, or effects on the workflow object). This is acceptable given the annotations, but the description contributes little beyond them.

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 two short sentences, with the purpose stated in the first sentence. Every word earns its place; there is no fluff or repetition. It is front-loaded with the main action, making it immediately clear.

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 simple, with a single parameter and an output schema (present but not shown in the prompt). The description fully captures the return value (JSON string) and the operation's nature (serialization). Given the annotations and output schema, no additional context is strictly necessary. It lacks any mention of edge cases or limitations, but for a straightforward export utility, the description is sufficiently complete.

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?

There is one parameter (workflow) with schema coverage of 0% in the description. The description merely repeats the parameter name and says 'workflow' without explaining the expected structure, required fields, or accepted formats. Since the schema uses additionalProperties: true, the description should clarify what constitutes a valid workflow object, but it does not. The low coverage requires compensation, which is absent.

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's purpose: exporting/serializing a workflow to a JSON string. This distinguishes it from siblings like comfy_import_workflow (which loads a workflow) and comfy_snapshot_workflow (which saves a persistent snapshot). The verb 'export/serialize' and resource 'workflow' 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when to export vs. snapshot vs. build). It simply states what it does without contextual hints or exclusions, leaving the agent to infer usage from the name alone.

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