pbs_snapshots_list

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

No annotations are provided, so the description carries full burden. It explicitly labels the tool as 'READ-ONLY', which is a key behavioral trait. It also lists the return metadata. It does not mention pagination, authorization, or rate limits, but for a read-only list operation, the core disclosure is sufficient.

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 two sentences, front-loaded with the purpose and key details. Every sentence adds value: first states functionality, second provides usage guidance and alternatives. No wasted words.

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?

Given the presence of an output schema and 100% parameter coverage in the schema, the description is sufficiently complete. It covers the operation's purpose, filters, return data, and relevant sibling tools. It does not explain the 'proximo_target' parameter, but that is detailed in the 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?

Schema coverage is 100%, so baseline is 3. The description mentions the filter parameters (namespace, backup_type, backup_id) and their allowed values, but this largely repeats the schema descriptions. It does not add significant new meaning beyond what is already in the schema.

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 the action ('list backup snapshots'), the resource ('in a PBS datastore'), and the scope ('with optional filters'). It also lists the returned metadata and distinguishes from sibling tools for deletion and modification.

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?

Explicitly provides when to use alternatives: 'To delete one use pbs_snapshot_delete; to change its protected flag or notes use pbs_snapshot_protected_set or pbs_snapshot_notes_set.' This gives clear guidance for selecting among related tools.

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