List volume backups

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

The description adds no behavioral details beyond what annotations already provide. Annotations indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description does not mention pagination, ordering, limits, or other behaviors typical for a list operation. It carries minimal extra value.

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 sentence that is concise and front-loaded. However, it is extremely brief and could be slightly expanded without losing conciseness. It efficiently communicates the core operation.

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?

The tool has low complexity (2 required params, no output schema). The description covers the basic purpose but lacks additional context such as the format of results, whether backups are sorted, or error handling. With annotations providing safety info, the description is minimally adequate but could be more helpful for a complete understanding.

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 input schema covers both parameters with descriptions, so the description does not need to add parameter details. There is no additional clarification or context beyond what the schema already provides, which meets the baseline for 100% schema coverage.

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 'List backups for a Docker volume' clearly states the verb (List) and the resource (backups for a Docker volume). It is specific and distinguishes from sibling tools that do different operations on volume backups, such as create, delete, list_files, or restore.

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. For example, it does not differentiate from 'arcane_volume_backup_list_files' or other listing tools. No context is given about prerequisites or conditions that affect usage.

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