list_snapshots

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

With no annotations, the description takes on the safety disclosure burden; it reveals ordering behavior and defines both possible kind values. It does not explicitly state that listing is side-effect free, but the verb 'list' makes this clear.

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?

Two short sentences front-load the core purpose, then add the key usage hint and kind definition. Every sentence earns its place with no repetition.

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 zero-parameter list tool with an output schema, the description supplies the essential context: when to call it and what ordering/filter values to expect. Nothing critical is missing.

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 the schema already covers all input requirements. The description adds useful context about result ordering and kind taxonomy, matching the baseline for parameterless tools.

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?

States a specific verb and resource ('list saved snapshots') plus ordering ('newest first'), and its list semantics clearly distinguish it from sibling save_snapshot/load_snapshot. The intent is unambiguous and actionable.

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?

Provides an explicit usage context: call this first during handover. It does not name alternatives or exclusions, but for a simple list operation no strong alternative is needed.

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