coolify_stop_database

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

With no annotations provided, the description carries the full burden. It adds '[DESTRUCTIVE]' and 'Causes downtime', which are useful behavioral traits. However, it does not disclose the requirement for the 'confirm' parameter, the role of 'docker_cleanup', or any authorization or side effects beyond downtime.

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 extremely concise with two short sentences, front-loading the destructive warning. Every sentence adds value with no redundancy.

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?

For a simple tool with 3 parameters and no output schema, the description is adequate but could be improved by explicitly noting that the 'confirm' parameter must be set to true for the operation to proceed. It covers the core purpose and a key effect (downtime) but lacks a few details that would make it fully self-contained.

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 baseline is 3. The description adds no information about the uuid, confirm, or docker_cleanup 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 explicitly states 'Stop a running Coolify database', which is a specific verb+resource combination. It clearly distinguishes from sibling tools like coolify_start_database, coolify_restart_database, and coolify_delete_database.

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 usage (stop a database) but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. The '[DESTRUCTIVE]' label hints at caution but is not a full guideline.

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