Update Database Backup Schedule

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

The description adds that only supplied fields change, aligning with idempotentHint=true. It does not disclose authorization needs or side effects beyond what annotations provide. Annotations already indicate non-destructive, read-only=false, and idempotent behavior.

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 sentences convey essential information without redundancy. The description is front-loaded with the action and resource.

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 the complexity (14 params, 3 required, no output schema), the description combined with schema descriptions provides sufficient context for a mutation tool. Could mention return behavior but adequate.

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 71%, so the baseline is 3. The description adds the concept of partial updates but does not detail individual parameters beyond what the schema already provides.

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 clearly states the verb 'Update' and the resource 'backup schedule'. It specifies that only supplied fields change, which distinguishes it from create (coolify_create_database_backup) and delete (coolify_delete_database_backup) operations.

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 for modifying existing backup schedules, but does not explicitly provide when-to-use vs alternatives or exclude certain scenarios. It provides context but lacks exclusions.

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