coolify_update_private_key

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Simply stating 'Update' implies a mutation, but there is no information about idempotency, error cases, authorization requirements, or side effects. This is insufficient for an agent to understand the tool's 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 extremely concise with a single sentence. It avoids fluff but at the cost of depth. However, for a simple update tool, this brevity is acceptable and arguably efficient.

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 lack of output schema, no annotations, and 4 parameters, the description is insufficiently complete. It does not clarify the required role of UUID, what happens on success/failure, or how the update interacts with other tools. The agent lacks critical context for safe invocation.

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 coverage is 100%, so the baseline is 3. The description adds no further meaning beyond the schema. It does not explain parameter constraints, data formats, or relationships between parameters. The agent must rely solely on the schema descriptions.

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 resource 'private key', which distinguishes it from sibling tools like 'create' and 'delete'. However, it does not specify which attributes can be updated or any scope, but the verb-resource pair is sufficiently clear.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., create or delete). There is no mention of prerequisites such as existence of the private key or required permissions. The agent has no decision context beyond the tool name.

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