appwrite_delete_collection

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

No annotations provided, so description carries full burden. Discloses critical destructive traits: irreversibility and cascade deletion of documents. However, omits other important behaviors like authentication requirements, side effects on collection indexes/attributes, or error conditions.

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 no redundancy. Front-loaded with the action verb. The '[UNIFIED]' prefix is slightly extraneous metadata but doesn't significantly detract from 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?

Adequately covers the safety-critical aspect (irreversible) for a destructive operation. However, given 3 undocumented parameters and no output schema, it lacks completeness regarding parameter semantics, success/failure behaviors, and related resource impacts (e.g., what happens to collection indexes).

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%, requiring the description to compensate. It adds no explanation for parameters like 'site' (ambiguous - Appwrite instance? Project?), 'database_id', or 'collection_id'. Relies entirely on parameter names which are partially self-descriptive but insufficient.

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?

Clearly states the action (Delete) and resource (collection) with specific cascade scope ('and all its documents'). This distinguishes it from sibling appwrite_delete_document by implying bulk deletion, though it doesn't explicitly name the sibling 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?

Lacks explicit guidance on when to use this versus alternatives (e.g., deleting individual documents vs the whole collection) or prerequisites like backup confirmation. Only provides an implied warning via 'irreversible'.

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