appwrite_update_document

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

Discloses partial update behavior (PATCH semantics) which is critical for mutation tools. However, missing safety context: no mention of error behavior for missing documents, idempotency, or return values. Annotations are absent, so description carries full burden.

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?

Extremely concise at two sentences. Front-loaded with action, though '[UNIFIED]' tag is extraneous noise that doesn't aid agent understanding.

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?

Insufficient for a 6-parameter mutation tool with zero schema documentation and no output schema. Missing critical context for required identifiers and error handling.

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 fails to compensate adequately. Mentions 'provided fields' vaguely referencing the 'data' parameter but provides no semantics for site, database_id, collection_id, document_id, or permissions identifiers.

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 action (Update) and resource (document) clearly. Implies single document operation (vs bulk) by singular noun, though could explicitly distinguish from sibling appwrite_bulk_update_documents.

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 partial usage guidance by specifying partial update semantics ('Only provided fields will be updated'). Lacks explicit when-to-use vs create_document or prerequisites like existence checks.

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