ecp_mongo_drop_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the operation is destructive and 'Irreversible,' which is critical for an agent deciding whether to invoke it. It does not add detail about confirmation requirements or side effects, but the core risk is clearly disclosed.

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 two short sentences with no filler. 'Drop (delete) a collection entirely' front-loads the action, and 'Irreversible' adds the most important behavioral warning concisely.

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 plus the explicit confirm=true schema constraint gives an agent the minimum needed to call the tool safely. However, it omits any discussion of when to use it versus alternatives, and with no output schema or annotations, slightly more context about expected effects would make it more complete.

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%, and the description adds no parameter-level explanation. It does not clarify that confirm must be true, nor does it define db_name or collection_name beyond their self-evident names. For a low-coverage schema, the description should compensate but does not.

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 a specific verb ('Drop'), the resource ('a collection'), and the full scope ('entirely'). This clearly distinguishes it from siblings like ecp_mongo_delete_document or ecp_mongo_create_collection, so an agent can recognize exactly what it does.

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 gives no explicit guidance on when to use this tool versus alternatives such as dropping a single document or truncating a collection. It does not mention exclusions, prerequisites, or safer alternatives; the intended usage is only implied by the name and description.

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