list_snapshots

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

The readOnlyHint annotation already signals a safe read operation. The description adds useful context by explaining snapshots are taken automatically before writes and are returned newest first, but it does not describe return shape, pagination, or any other behavioral details beyond the annotation.

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?

One short sentence front-loads the key fact that snapshots are automatic pre-write captures and ends with ordering. It is concise and efficient, though the implicit 'list' action could be more explicit.

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 read-only tool with one required parameter, the core concept and ordering are present. However, the lack of any return-format detail and minimal explanation of the source parameter leaves some gaps an agent must infer.

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?

With 0% schema description coverage, the description must compensate, but it only says 'this source' without defining what a source is, what value is acceptable, or how to specify it. This adds minimal meaning beyond the required string property.

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 conveys that this tool returns snapshots associated with a sourceanding the 'this source' context, and the 'newest first' ordering strongly implies a list operation. It is reasonably distinguishable from restore_snapshot and other siblings, though it lacks an explicit verb such as 'lists'.

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 restore_snapshot. The description implies snapshots exist for review, but it does not state when listing is appropriate, what prerequisites exist, or which sibling tools to prefer in other scenarios.

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