comfy_delete_snapshot

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Destructive' label adds little. However, it does disclose the confirmation elicitation behavior, which is beyond annotations. No contradiction found.

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 concise with a clear structure: a one-line summary followed by parameter details. It front-loads the destructive nature and keeps the parameter explanations brief. No wasted 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?

The tool has an output schema and only 2 parameters, so the description is mostly sufficient. However, it doesn't mention what happens after deletion (e.g., irreversibility, impact on related workflows) or any prerequisites. Given the destructive nature, a bit more context would help.

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 0%, so the description must compensate. It explains snapshot_id and confirm parameters, including the default behavior of confirm. This adds meaning beyond the schema's basic type/default info, but could be more detailed about the elicitation process.

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 deletes a snapshot and flags it as destructive. It distinguishes from siblings like comfy_restore_snapshot and comfy_list_snapshots by the verb 'delete' and the resource 'snapshot'.

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 explains the confirm parameter's role in elicitation but does not explicitly state when to use this tool versus alternatives like comfy_delete_history or comfy_clear_queue. It implies usage for deleting snapshots but lacks explicit when/when-not guidance.

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