coolify_delete_private_key

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

The description notes the destructive nature with '[DESTRUCTIVE]' and the condition 'Blocked if in use'. These are valuable behavioral hints. However, it fails to mention the confirm parameter, which is critical for executing the destructive operation. Without annotations, the description carries full burden and misses this key safety 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?

The description is very concise, using one sentence plus a tag. It is front-loaded with the destructive marker. However, it omits necessary context about the confirm parameter, which would only add minimal length. Slightly under-specified for safe operation.

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 delete tool with 2 parameters and no output schema, the description should cover the confirm requirement and what the user expects after deletion. It mentions the block-if-in-use constraint but ignores the confirm parameter, which is critical for operation. This leaves the agent potentially unaware of required confirmation, making the tool hazardous to use incorrectly.

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 baseline is 3. The description adds no additional parameter information beyond what the schema already provides (uuid and confirm explanations). It does not compensate for or enrich the semantic understanding of the parameters.

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 'Delete an SSH private key', providing a specific verb and resource. The tool name includes 'delete_private_key', so there is no ambiguity. It distinguishes itself from sibling tools like coolify_create_private_key or coolify_list_private_keys through clear naming and action.

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 offers no guidance on when to use this tool versus alternatives (e.g., list keys first or use update). It does not mention prerequisites or scenarios where deletion is appropriate. The only contextual hint is 'Blocked if in use', but that is a constraint rather than usage direction.

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