coolify_list_database_backups

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

With no annotations, the description must fully convey behavioral traits. It only states the action but does not clarify if the operation is read-only, what constitutes a 'backup' (configuration vs. snapshots), whether authentication is required, or any side effects. This leaves significant ambiguity.

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, clear sentence with no unnecessary words. It is appropriately succinct for a simple list operation, though it could be front-loaded with key behavioral notes if needed.

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 description omits what the response contains (e.g., backup IDs, timestamps, status) and does not mention pagination, ordering, or typical usage patterns. For a list tool without an output schema, this leaves the AI agent guessing about the return structure.

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 for the single parameter 'uuid' is 100% with description 'UUID of the database'. The tool description adds no additional meaning beyond the schema, so the 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 'List backups for a specific database' clearly states the action (list), the resource (backups), and the scope (specific database). It effectively distinguishes from siblings like 'coolify_list_backup_executions' (which lists backup runs) and various create/delete backup tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'coolify_list_backup_executions' or how to pair it with 'coolify_create_database_backup' or 'coolify_delete_database_backup'. The description lacks usage context or prerequisites.

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