appwrite_bulk_delete_documents

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

No annotations are provided, so the description carries full burden. While 'Delete' implies destruction, there is no explicit warning about irreversible data loss, no mention of partial vs atomic failure behavior, permissions required, or rate limits for bulk operations.

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 single sentence is efficient and front-loaded, but the '[UNIFIED]' tag adds noise without value. More importantly, for a destructive 4-parameter operation with zero schema documentation, the description is underspecified rather than appropriately concise.

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?

Given the complexity (destructive bulk operation, 4 required parameters, 0% schema coverage, no annotations, no output schema), the description is grossly incomplete. It lacks parameter explanations, behavioral warnings, and usage context necessary for safe 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?

With 0% schema description coverage, the description must compensate for undocumented parameters (site, database_id, collection_id, document_ids). It completely fails to do so, leaving the agent with no semantic understanding of what these parameters represent or their expected formats.

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 verb (Delete), resource (documents), and scope (multiple/at once), which distinguishes from sibling 'appwrite_delete_document' (single) and 'appwrite_bulk_delete_files' (files). However, the '[UNIFIED]' prefix is unexplained metadata noise that slightly diminishes clarity.

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 no guidance on when to use this versus single-document deletion, no prerequisites (e.g., needing document IDs beforehand), and no warnings about the destructive nature of the operation.

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