List Snapshots

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds a Returns section detailing the fields in the snapshot array (type, ID, timestamp, etc.), which goes beyond annotations and helps the agent understand the output.

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 concise and well-structured with 'Args:' and 'Returns:' sections. The Args list largely duplicates the schema, but the overall length is still reasonable and the purpose is front-loaded. No waste but some redundancy.

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?

There is no output schema, but the description includes a Returns section that lists the snapshot fields, which compensates. All parameters are covered, and annotations provide safety context. It doesn't discuss error conditions or pagination, but for a simple read-only list tool, the description is fairly complete.

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 coverage is 100%, and the description essentially restates the parameter descriptions found in the schema. It adds minimal new meaning beyond what's already in the input schema, so a baseline of 3 is appropriate.

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 the specific verb 'List' with the resource 'snapshots in a datastore' and mentions optional filtering by backup type and ID. This clearly distinguishes it from sibling tools like pbs_list_tasks or pbs_list_datastores.

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 makes the purpose clear: list snapshots with optional filters. It doesn't explicitly state when to use this tool over alternatives, but the resource is unambiguous and the filtering options are described. No exclusions are provided, but the context is clear enough.

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