Delete Coolify Database

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

Annotations already provide destructiveHint: true, so the description's warning adds little new information. It does not disclose any other behavioral nuances like irreversibility or audit logging, which would be beneficial beyond the annotation.

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 one short sentence plus a warning. It is extremely concise with no wasted words, and the warning is front-loaded for immediate awareness.

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 destructive nature annotated, the description provides sufficient context for a delete operation. It could benefit from explicitly stating irreversibility, but the warning covers the critical risk. Output schema is absent, but for a delete tool, return details are less critical.

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 the schema already explains all parameters. The description adds no additional parameter explanations, relying entirely on the schema. Baseline 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 clearly states 'Delete a database resource' with a specific verb and resource. Among many sibling tools with 'delete' prefixes, this one uniquely targets databases, distinguishing it from other delete 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?

The description includes a prominent warning about destructive behavior, implying when to use (intentional deletion). However, it does not explicitly state when not to use or suggest alternatives like disabling the database instead.

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