appwrite_bulk_update_documents

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

No annotations provided, so description carries full burden. It only states the operation type (update) but lacks critical behavioral details: whether updates are partial or full replacements, error handling on invalid document IDs, atomicity guarantees, or required permissions.

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?

Single sentence that front-loads the action. Efficientlyworded, though the '[UNIFIED]' prefix appears to be implementation metadata that doesn't aid tool selection.

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?

Severely incomplete for a 4-parameter mutation operation with no annotations and no output schema. Fails to document the updates array structure, error scenarios, or prerequisites (e.g., existing database/collection requirements).

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 parameter guidance. The 'updates' array structure (what fields each object requires) is completely undocumented, leaving the agent guessing how to construct valid requests.

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 'Update multiple documents at once' which identifies the verb (update), resource (documents), and distinguishes from the sibling 'appwrite_update_document' (singular) by specifying 'multiple'. The '[UNIFIED]' prefix is noise but doesn't obscure the core purpose.

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 prefer bulk updates over single updates, constraints (e.g., all documents must be in the same collection), or transactional behavior (atomic vs partial success). The agent must guess whether to use this vs appwrite_update_document.

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