appwrite_bulk_create_documents

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

No annotations provided, so description carries full burden. It discloses efficiency characteristics and document structure requirements through the example. However, it omits critical behavioral details for a bulk mutation: atomicity guarantees, partial failure handling, rate limits, or return value structure.

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?

Front-loaded with clear purpose statement followed by concrete JSON example. The '[UNIFIED]' prefix is minor noise but acceptable. Example is necessary given the complex nested structure of the documents parameter. No redundant or tautological language.

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?

adequately covers the primary complex parameter (documents) but leaves significant gaps for the remaining required parameters. With no output schema and no annotations, a bulk creation tool should ideally disclose transaction boundaries or success/failure modes, which are absent.

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 coverage is 0%, requiring description to compensate. It provides excellent documentation for the complex 'documents' parameter with JSON examples and field constraints (document_id patterns, data object requirements). However, it completely omits semantics for 'site', 'database_id', and 'collection_id', leaving 3 of 4 required parameters undocumented.

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?

Description explicitly states 'Create multiple documents at once' with specific verb and resource. It distinguishes from sibling tool 'appwrite_create_document' by noting it's 'More efficient than creating one by one', clearly positioning it as the bulk alternative.

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?

Implies when to use via efficiency comparison to single creation, but lacks explicit guidance on when NOT to use (e.g., transactional requirements, error handling needs) or explicit naming of the single-document alternative. No prerequisites mentioned despite requiring site/database/collection context.

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