slide_list_snapshots

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

With no annotations, the description carries the burden. It adds useful context that snapshots come from successful backups and are filterable by location/deletion state, but it does not mention read-only behavior, default filters, pagination, sorting, or response format. For a list operation, this is adequate but not rich.

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 a single, efficient sentence that leads with the action and resource, then highlights the most decision-relevant filter dimensions. There is no redundancy with the schema.

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 10-parameter list tool with no output schema and no annotations, the description provides the essential scope but relies heavily on the schema for defaults, enums, and time formats. It would be stronger if it explicitly mentioned the default non-deleted location filter or pagination behavior.

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 100%, so the baseline is 3. The tool description only groups parameters at a high level ('by agent, location/deletion state, and backup start/end time range') without adding syntax or semantic detail beyond what the schema already provides.

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 uses a specific verb and resource ('List snapshots') and adds a meaningful scope qualifier ('taken as part of a successful backup'), plus the key filter dimensions. It is clear enough to distinguish from slide_get_snapshot, though it does not explicitly contrast with sibling tools like slide_list_backups.

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 implies usage as a filtered list operation and states the main filtering dimensions, but it does not explain when to prefer this over slide_list_backups or slide_get_snapshot. No exclusions or alternative tool names are given.

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