appwrite_delete_database

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

With no annotations provided, the description carries the full burden and successfully discloses two key behavioral traits: the cascading nature (collections are deleted too) and the irreversible nature of the operation. It appropriately signals destructive impact.

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 with zero waste—first defines the action, second states the irreversibility constraint. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't significantly impede readability. Appropriately front-loaded.

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?

Adequate for a destructive operation given the safety warnings provided, but incomplete due to missing parameter semantics and lack of return value description (no output schema exists). Sufficient for tool selection but not rich enough for confident invocation.

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% for both required parameters (site, database_id). While 'database_id' is somewhat inferable from context, 'site' is ambiguous (could be endpoint, project ID, or name) and remains undocumented. The description fails to compensate for the lack of schema documentation.

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?

States specific action (Delete) and resource (database) clearly. The phrase 'and all its collections' effectively distinguishes this from the sibling appwrite_delete_collection tool by clarifying the cascading scope 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?

Includes critical usage guidance with 'This action is irreversible,' which warns against casual use. However, it lacks explicit guidance on when to choose this over alternatives (e.g., appwrite_delete_collection for partial cleanup) or prerequisites like permissions.

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