comfy_diff_snapshots

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

Annotations already declare readOnlyHint=trueament, idempotentHint=true, destructiveHint=false, so the operation is known to be safe. The description adds that it returns a JSON with specific fields (added_nodes, removed_nodes, modified_nodes, total_changes), which is useful. No contradictions.

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 compact and front-loaded with the main purpose. It includes an Args section and Returns section, which is well-structured. No fluff, but the param descriptions are minimal (just names), which could be improved but does not waste words.

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 the tool has an output schema, the return types don't need to be fully described. However, the description doesn't explain the exact semantics of parameters (e.g., what if both id_b and current_workflow are set? What if only id_a? What does 'modified_nodes' mean?). The tool is relatively simple, but the param semantics gap makes it incomplete.

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 coverage is 0%, and while the description provides a brief args list, it doesn't add meaning beyond what the schema already includes (id_a, id_b, current_workflow). It doesn't explain formats, constraints, or how to choose between id_b and current_workflow. The description only lists names, similar to the schema titles, so minimal added value.

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 it diff two snapshots or a snapshot vs current workflow, using specific verbs ('Diff') and specifying the resources (snapshots and workflow). It distinguishes from siblings like comfy_snapshot_workflow and comfy_restore_snapshot by focusing on comparison, not creation or restoration.

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 clear usage context: it can compare two snapshots or a snapshot against the current workflow. It implies when to use it (for comparing states), but does not explicitly state when not to use it or suggest alternatives. However, the context is clear enough for an agent to decide.

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