delete_collectionDelete every document in a collection at once (useful to re-seed). Irreversible. To destroy the entire database, use delete_database instead.
| Name | Required | Description | Default |
|---|---|---|---|
| db | Yes | The database URL returned at creation (or its bare s-... capability). | |
| collection | Yes | Collection name (created implicitly on first write). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description notes 'Irreversible' and implies bulk deletion, which are critical behavioral traits. Since no annotations are provided, the description carries the full burden but could disclose more about side effects (e.g., whether the collection structure remains) or required permissions.
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?
Two sentences, front-loaded with the primary action and purpose. Every word earns its place, with no filler. Efficiently provides usage context and an alternative.
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 simple destructive tool with full schema coverage and no output schema, the description covers purpose, irreversibility, and distinguishes from a sibling. It could mention what happens to the collection structure itself, but overall it is quite 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 100%, so the schema already documents both parameters. The description adds no additional semantic information about the parameters, so baseline score of 3 applies.
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 'Delete every document in a collection at once', which is a specific verb and resource. It also distinguishes from sibling 'delete_database' by mentioning an alternative.
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?
Provides a use case ('useful to re-seed') and explicitly contrasts with 'delete_database'. However, it does not mention when not to use or other alternatives like 'delete_document'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, with descriptions that differentiate similar operations (e.g., create_database vs pro_create_database vs pro_attach_database). Agents can easily select the correct tool.
Most tools follow a verb_noun snake_case pattern, but 'database_status' is noun_verb. The 'pro_' prefix is consistently used for Pro account tools. Overall pattern is clear and predictable.
16 tools cover the full lifecycle of temporary databases, document CRUD, collection management, and Pro account operations. Each tool is justified and the count feels well-scoped for the domain.
The tool surface provides complete CRUD for documents, database lifecycle (create, delete, extend, status), and full Pro account management (checkout, cancel, create, attach, list). No obvious gaps for the stated purpose.