ecp_postgres_delete_database

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

The description explicitly warns 'Irreversible,' which is a key behavioral trait for a destructive operation. However, it provides no further details about cascading deletions, user permissions, or system effects that might be expected. Since no annotations are present, this single warning carries the burden but is insufficient for full transparency.

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 extremely concise, consisting of two short sentences. Every word serves a purpose: it states the action and the key risk (irreversibility). No filler or redundant phrasing.

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 complete enough for a simple destructive operation but lacks details about required parameters, effects on dependent objects, or any output. It does not mention that 'confirm' must be set to true, though the schema enforces it. A more complete description would explain typical usage and consequences.

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 schema provides no descriptions for 'db_name' or 'confirm', and the tool description does not explain them either. While parameter names are somewhat self-explanatory, the purpose of the 'confirm' boolean (must be true) is not stated, leaving an agent to rely on naming conventions rather than explicit semantics.

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 'Delete a Postgres database' clearly identifies the action (delete) and the resource type (Postgres database), distinguishing it from other database operations among siblings. The irreversibility note reinforces the specific nature of the operation.

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 usage guidance is provided. The description does not indicate when to use this tool versus other Postgres operations (e.g., drop table, truncate) or mention any prerequisites or consequences beyond irreversibility. An agent is left to infer the appropriate context from the name alone.

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