coolify_create_integration_token

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

With no annotations, the description usefully discloses that this is a WRITE operation and that Coolify validates the token against the provider before saving. However, it does not state required permissions, whether the token can be retrieved later, failure behavior, or other side effects.

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 compact sentences, front-loaded with the [WRITE] marker and the core action. There is no redundant or wasted text.

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?

The description covers purpose, write behavior, validation, and version, which is useful. But with no annotations and no output schema, it leaves gaps around authorization requirements, post-creation behavior, and what the operation returns.

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 75%, and the schema itself describes token formats and provider-specific metadata fields in detail. The description names the providers but adds little parameter-level meaning beyond the schema, so baseline adequacy 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 states a specific verb and resource: "Store a Doppler, Infisical, or HashiCorp Vault token," with team scope and version context. It is clear, though it does not explicitly distinguish this tool from sibling secret-management operations such as coolify_update_application_secret_manager.

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?

Usage is implied by the secret-manager token context and the Coolify v4.4+ note, but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives. The agent can infer the intended context but is not routed against close siblings.

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