coolify_set_database_storage_backup

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

The description does disclose that this is a write operation that creates or replaces a backup schedule, which is a meaningful behavioral trait beyond the schema. However, with no annotations provided, it fails to mention side effects such as overwriting existing schedules, permission requirements, or whether a backup is triggered immediately.

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 with a front-loaded [WRITE] tag and no filler. It is concise, though slightly too terse for a 15-parameter tool with significant sibling ambiguity.

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 no output schema, no annotations, and a complex 15-parameter surface, the description is far too sparse. It omits prerequisites, return behavior, side effects, and any differentiation from the many sibling backup tools, leaving the agent to guess critical details.

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 adds no information about any of the 15 parameters. Schema descriptions cover roughly 60% of parameters, but the description does not compensate for the undocumented retention_* fields or clarify relationships like save_s3 and s3_storage_uuid.

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 states a specific action ('Create or replace') on a specific resource ('database persistent volume/directory'), which clearly identifies the tool's core purpose. It is distinguishable from run/delete backup siblings, though it does not explicitly contrast with create/update backup tools like coolify_create_database_backup or coolify_update_database_backup.

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?

There is no guidance on when to use this tool versus sibling alternatives such as coolify_create_database_backup, coolify_update_database_backup, coolify_run_database_storage_backup, or coolify_set_application_storage_backup. The agent must infer selection criteria entirely from the tool name and description.

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