coolify_create_database_mongodb

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'Create a MongoDB database' without mentioning any side effects, required permissions, or mutability. The absence of any behavioral context leaves the agent with minimal insight beyond the obvious fact that this is a creation tool.

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 that is clear and front-loaded. It is concise and free of unnecessary words. However, it could be slightly expanded to include context without losing conciseness, earning a 4 rather than 5.

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 is minimal and does not explain the overall process, return values, or error conditions. The schema covers parameters, but the tool's behavior in the broader workflow is not described. With 10 parameters and no output schema, a slightly more detailed description would improve completeness. Currently meets the minimum viability.

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?

The input schema has 100% parameter description coverage, so the schema itself explains the parameters adequately. The description adds no additional meaning beyond what the schema provides. Baseline of 3 is appropriate given high schema coverage.

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 ('Create') and resource ('MongoDB database'), making it unambiguous. It effectively distinguishes from sibling tools like 'coolify_create_database_postgresql' by specifying the exact database type.

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 that the tool is used to create a MongoDB database, but it does not provide explicit guidance on when to choose this over other database types or mention prerequisites (e.g., existing project/server). With many sibling database creation tools, more explicit usage context would be beneficial.

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