list_batch_backups

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action without describing what 'available' means, whether results are paginated, sorted, or filtered, what authentication is required, or what the output format looks like. This leaves significant behavioral questions unanswered.

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 extremely concise at just four words, front-loading the essential action and resource. There's zero wasted language or redundancy, making it maximally efficient while still communicating the core purpose.

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 tool has an output schema (which handles return values) and only one simple parameter, the description's minimalism is somewhat acceptable. However, for a data listing operation with no annotations, it should ideally provide more context about what constitutes 'available' backups and how results are presented.

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 description mentions no parameters at all, while the schema has one parameter ('limit') with 0% description coverage. Since the schema provides the parameter definition but no semantic context, and the description adds nothing about parameters, this meets the baseline for minimal parameter documentation.

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 verb ('List') and resource ('available batch backups'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'restore_batch_backup' or explain what distinguishes batch backups from other backup types in the system.

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 provides no guidance on when to use this tool versus alternatives like 'restore_batch_backup' or other list operations. There's no mention of prerequisites, typical use cases, or when this specific listing function is appropriate versus other data retrieval methods.

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