coolify_update_service_env

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

With no annotations provided, the description lacks any behavioral context. It does not disclose side effects (e.g., overwriting, whether the update is immediate), authorization requirements, or what happens if the variable does not exist.

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 a single sentence, which is concise but overly minimal. It fails to provide context that justifies its brevity; a slightly longer description would be more helpful without adding excessive length.

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 high schema coverage but no output schema, the description is incomplete. It does not mention return values, confirmation of the update, or potential errors, leaving the agent without crucial operational context.

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?

Although the schema has 100% coverage, the description adds no extra meaning to the parameters. It merely repeats the action without elaborating on how parameters like 'key', 'value', 'uuid', and 'env_uuid' are used in the update process.

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 action ('Update') and the resource ('service environment variable'), distinguishing it from sibling tools like 'create' and 'delete'. However, it could be more specific about which aspects of the environment variable are updated (e.g., key, value).

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 given on when to use this tool versus alternatives like 'create' or 'delete'. The description does not mention prerequisites, such as having an existing environment variable, or when updating is preferred over creating.

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