list_snapshots

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List saved snapshots' and does not disclose what a snapshot is, where they are stored, whether the list is sorted, whether it includes metadata, or whether any side effects occur. The bilingual text is redundant and does not add behavioral context.

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 short and front-loaded with the core statement, but the Korean duplicate ('저장해 둔 스냅샷 목록.') is redundant for an English-language tool description and adds no information. It is concise but not optimally structured; one sentence would suffice.

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, so return values may be documented there, but the description still lacks context about what 'snapshots' are in this domain, how they relate to sibling tools like 'snapshot' and 'restore', and whether listing has any side effects. For a tool with no annotations and no parameter guidance, the description is too thin to fully orient an agent.

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?

The tool has zero parameters, so there is no parameter semantics burden on the description. The schema is trivially complete (100% coverage with no properties), and the description correctly implies a no-argument listing operation. Baseline 4 is appropriate for a zero-parameter tool.

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 states a clear verb and resource ('List saved snapshots'), so an agent can tell it is a read-only listing operation. However, it does not distinguish it from the sibling tool 'snapshot' or from 'restore'/'save_blend', which are related snapshot operations. The bilingual repetition adds no semantic value.

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?

No guidance is given about when to use this tool versus alternatives like 'snapshot' or 'restore'. The description simply states what it does, leaving the agent to infer that it is for browsing saved snapshots. There is no mention of prerequisites, typical use cases, or exclusions.

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