appwrite_delete_file

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

No annotations are provided, and the description fails to disclose critical behavioral traits: whether deletion is permanent or recoverable, required permissions/authorization levels, or potential side effects. For a destructive operation, this is a significant gap.

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 core sentence is appropriately concise, but the '[UNIFIED]' prefix appears to be implementation metadata that adds no value to the agent. The extreme brevity is insufficient given the lack of schema 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 operation with three undocumented parameters and no output schema, the description is inadequate. It should explain parameter relationships (bucket containing file) and deletion scope.

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%, and the description provides no compensation for this gap. It does not explain what 'site', 'bucket_id', or 'file_id' represent, their formats, or how to obtain them.

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 tool deletes a file from storage using specific verb and resource. However, it does not explicitly distinguish from sibling appwrite_bulk_delete_files (though 'a file' implies singularity).

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 single-file deletion versus the bulk_delete_files sibling, nor any prerequisites for obtaining the required bucket_id or file_id parameters.

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