directus_create_items

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

No annotations are provided, so the description carries the full burden. While 'Create' implies mutation, there's no disclosure of atomicity (all-or-nothing vs partial failure), limits on batch size, idempotency, or what happens on validation errors for individual items.

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?

Brief at one sentence, but the '[UNIFIED]' tag at the beginning is structural noise. Otherwise efficient.

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 4-parameter mutation tool with zero schema coverage and no output schema, the single-sentence description is inadequate. Missing: parameter formats, partial failure behavior, and return structure.

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 must explain the four parameters (site, collection, data, fields). It fails entirely—no explanation of 'site' (instance identifier?), 'collection' (name vs ID), 'data' array structure (schema of items), or 'fields' (projection/filter?).

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 states a clear action ('Create') and resource ('multiple items in a collection'), and explicitly distinguishes this from the singular sibling tool 'directus_create_item' by emphasizing 'multiple items' and 'at once'. However, the '[UNIFIED]' prefix is noise that doesn't add meaning.

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 this batch tool versus the singular 'directus_create_item', or versus similar appwrite_bulk_create_documents. No prerequisites mentioned (e.g., collection existence, permissions).

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