coolify_list_backup_executions

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

With no annotations provided, the description must disclose behavioral traits. It merely states it lists executions, but does not mention that it is read-only, non-destructive, or any side effects. The agent cannot infer safety or impact beyond the name.

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, grammatically complete sentence with no unnecessary words. It is front-loaded and highly efficient.

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 2 required parameters and no output schema. The description does not explain the return format, pagination, ordering, or what constitutes an 'execution'. For a list tool, this is insufficient to fully inform the agent about expected results.

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% with clear descriptions of both 'uuid' (UUID of the database) and 'backup_uuid' (UUID of the scheduled backup). The description adds no additional meaning beyond what the schema already provides, meeting the baseline.

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 executions of a database backup schedule' clearly states the action (list) and the resource (executions) with context (database backup schedule). It distinguishes from siblings like coolify_list_database_backups (lists schedules) and coolify_delete_backup_execution (deletes executions).

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 explicit guidance on when to use this tool vs alternatives. It implies usage when you have a database and backup schedule UUID, but does not state when not to use it or mention sibling tools like coolify_list_database_backups or coolify_delete_backup_execution.

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