dokploy_database

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

With no annotations, the description carries full burden. It discloses some behavior (e.g., get returns masked env summary, getEnvValuesUnsafe is 'UNSAFE escape hatch'), but omits side effects, auth needs, rate limits, or data sensitivity for mutation actions like update/remove.

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 dense but efficient, using dots and semicolons to separate actions. It packs much information without redundancy, though it could benefit from bullet points for readability.

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 tool's complexity (27 params, 16 actions), the description covers most input scenarios and per-engine rules. However, it lacks explanation of return values, errors, or what 'move' and 'reload' do exactly, and there is no output schema.

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 low (37%), but the description extensively explains per-action and per-engine parameter requirements (e.g., 'postgres/mysql/mariadb: REQUIRE databaseName+databaseUser', 'redis: only databasePassword'). This adds critical meaning beyond the schema.

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 starts with 'Manage databases (postgres/mysql/mariadb/mongo/redis/libsql).' and enumerates all actions, providing a clear verb+resource mapping. It distinguishes from sibling tools (dokploy_application, etc.) by focusing solely on database operations.

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 by listing actions and per-engine requirements, but does not explicitly state when to use this tool vs alternatives or provide exclusions. No 'when-to-use' or 'when-not-to-use' guidance is given.

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