comfy_list_snapshots

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is fully covered. The description adds the 'newest first' ordering and the structured SnapshotList return type, which is moderate value beyond annotations but similar to the calibration baseline for read-only tools.

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?

Roughly 25 words, front-loaded with the main purpose, with a compact Args block for the single parameter. Every sentence earns its place with no fluff.

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?

For a simple, single-param tool with an output schema and complete annotations, the description captures everything needed: operation, ordering, and return shape. Nothing material is missing given the tool's low 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?

Schema description coverage is 0%, but the description compensates for the single parameter by explaining that 'limit' is the 'Maximum number of snapshots to return (default 20)', which adds meaning beyond the bare schema field. Fully documents the only parameter present.

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 phrase 'List workflow snapshots (newest first)' provides a specific verb (list), resource (workflow snapshots), and ordering semantics. This clearly distinguishes it from sibling snapshot tools like comfy_snapshot_workflow, comfy_restore_snapshot, and comfy_delete_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 makes the basic operation clear and explains the limit default, so context is implied. However, it never explicitly mentions when to use this over alternatives (e.g., comfy_list_jobs or comfy_auto_snapshot) and offers no exclusions, so it meets only the baseline for guidance.

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