coolify_create_backup_config

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

Annotations are all false, so the description carries the transparency burden. It adds behavioral context not in annotations: 'Cron expression is validated' and 'Audit: coolify.database_backup_config.create' disclose validation and audit behavior. No contradictions exist.

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?

Two concise sentences deliver purpose, a key behavioral note, and audit information without waste. The description is front-loaded with the primary action and every sentence adds value.

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?

Despite having 5 parameters and no output schema, the description covers the essential purpose and one key constraint (validation). The schema handles parameter details. It could mention return value or on-success behavior, but for a straightforward create operation this is sufficient.

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 description coverage is 100%, so parameters are already fully documented. The description's mention of cron validation adds minimal value beyond the schema's 'Cron expression for backup schedule'. Baseline 3 is appropriate since the schema does the heavy lifting.

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 uses a specific verb 'Create' and resource 'backup configuration for a database', clearly distinguishing it from sibling tools like coolify_update_backup_config and coolify_list_database_backups. It unambiguously states what the tool does.

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 implies use when creating a new backup configuration for a database, but does not explicitly mention alternatives or exclusions. It provides clear context without naming when to use this tool over update_backup_config or list_database_backups, so it falls short of a 5.

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