dokploy_database

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

No annotations exist, and the description does not disclose behavioral traits beyond listing actions. For example, it does not explain side effects (e.g., whether 'remove' is permanent), authentication needs, or rate limits. The focus is on parameter requirements rather than operational 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 a single dense paragraph that packs a lot of information. While front-loaded with the purpose, it could benefit from bullet points or separate sections for clarity. It is not overly long but lacks structural conciseness.

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 25 parameters, low schema coverage (32%), and no output schema or annotations, the description covers most parameter dependencies per engine and action. However, it omits behavioral details for actions like 'reload' vs 'deploy', and does not mention return values. Still, it provides substantial 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?

With only 32% schema coverage, the description adds substantial meaning by explaining which parameters are required for each database engine. It clearly lists conditions like 'postgres/mysql/mariadb: REQUIRE databaseName+databaseUser' and 'redis: only databasePassword', going 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 clearly states the tool's purpose: 'Manage databases (postgres/mysql/mariadb/mongo/redis/libsql)' and enumerates specific actions. This identifies the resource and operations, distinguishing it from sibling tools that manage other resources.

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 provides detailed per-engine parameter requirements for the 'create' action, but does not offer guidance on when to use this tool versus alternatives. There is no explicit statement of when-not to use or mention of similar tools, though siblings cover different resources.

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