appwrite_bulk_delete_files

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 fails to mention that this is a destructive/irreversible operation, doesn't describe partial failure behavior, success confirmation, or rate limiting implications 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 description is brief, but the '[UNIFIED]' prefix adds noise without value. The core sentence is front-loaded and efficient, though the metadata tag wastes space that could have been used for parameter or behavioral documentation.

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 destructive bulk operation with 3 parameters (0% schema coverage), no output schema, and no annotations, the description is dangerously thin. It lacks critical context about transaction boundaries, authentication scope, and what confirmation (if any) is returned after deletion.

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 has 0% description coverage, so the description must compensate. While 'from a bucket' loosely implies bucket_id and 'multiple files' implies file_ids, it completely omits the 'site' parameter (critical for multi-tenant setups) and provides no format guidance for the file_ids array items.

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 the action (Delete) and resource (multiple files from a bucket), distinguishing it from the singular appwrite_delete_file sibling. However, the '[UNIFIED]' prefix is metadata noise that doesn't aid clarity, and it doesn't explicitly contrast with the Directus file deletion tools.

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?

No guidance provided on when to use this bulk operation versus the single-file appwrite_delete_file, or how to handle partial failures. No prerequisites or alternative approaches are mentioned.

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