appwrite_create_document

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

No annotations provided, so description carries full burden. Adds valuable behavioral note that document_id 'unique()' triggers auto-generation. However, missing critical mutation details: idempotency behavior, conflict resolution (what if ID exists?), required permissions, or validation rules.

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?

Two sentences, front-loaded with purpose. Efficient length. Minor deduction for '[UNIFIED]' metadata noise 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?

With 6 parameters (including nested objects), 0% schema coverage, no annotations, and no output schema, this description is insufficient. Missing explanations for hierarchical relationships (site/database/collection) and data payload structure required to invoke tool correctly.

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 (<50% threshold), so description must compensate heavily. Only partial compensation for document_id parameter mentioning 'unique()' syntax. Zero explanation for site, database_id, collection_id, data structure, or permissions format despite 5 required parameters.

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 (Create) and resource (document) clearly. '[UNIFIED]' prefix is noise metadata. Does not explicitly distinguish from sibling appwrite_bulk_create_documents (plural vs singular implied but not stated).

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 on when to use this single-document tool vs appwrite_bulk_create_documents, or vs appwrite_update_document. No prerequisites or conditions mentioned.

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