ecp_mongo_delete_database

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

The description explicitly notes 'Irreversible,' which is a key behavioral trait that goes beyond the name. However, with no annotations, the description carries the full burden. It does not disclose side effects like impact on associated users, collections, or data recovery options. The irreversibility is mentioned, but other destructive implications are omitted.

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, concise sentence with no fluff. It front-loads the essential information (action and irreversibility). For a tool with two parameters, this is appropriately brief, though it sacrifices detail for 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?

For a destructive operation with no annotations and no param descriptions, the description is inadequate. It does not explain the confirmation flow, the effect on the database, or any prerequisites. A minimal description should at least note that confirm=true is required and that the operation cannot be undone. The current text is too sparse for safe usage.

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 description coverage is 0%, so the description must explain parameters. It does not mention db_name or confirm at all. The confirm parameter's requirement (must be true) is only in the schema, not in the description. This is a complete failure to clarify parameter meaning.

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 the exact action ('Delete') and resource ('MongoDB database'), and adds critical information about irreversibility. This clearly differentiates it from other delete-database tools (mysql, mssql, postgres) based on the MongoDB context.

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 provided on when to use this tool versus alternatives. There is no mention of safety conditions, prerequisites, or when not to use it. A destructive operation like this should at least hint at confirmation requirements, but the description only states the action.

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