list_snapshots

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

With no annotations present, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not explicitly state that it is non-destructive, what data is returned, whether pagination applies, or what a 'snapshot' entails in this 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 very short and front-loads the main verb and object. It is appropriately concise for a zero-parameter tool, though it is slightly too terse to provide helpful context beyond the bare operation.

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 no-parameter list operation, this is minimally adequate: an agent knows to call it to get saved snapshots. However, it is missing context about what a snapshot is, how they relate to other snapshot tools, and what the returned data will look like, especially given that there is no output schema.

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 no input parameters, so the absence of parameter details in the description is not a gap. The schema already conveys that there is nothing to configure. No additional parameter explanation is necessary.

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 a specific action ('List') and a specific resource ('saved snapshots'), so an agent can infer the tool's basic purpose. It doesn't explicitly differentiate from sibling snapshot-related tools like snapshot_library or changes_since, but the 'list' verb makes the operation reasonably distinct.

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 provided about when to use this tool instead of alternatives such as snapshot_library or changes_since. The description does not mention any exclusions, prerequisites, or relationship to other snapshot operations.

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