directus_import_items

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

No annotations provided, so description carries full burden. Fails to disclose import behavior details: validation rules, atomicity (partial vs full failure), idempotency, or return structure. Schema shows data array input but doesn't explain expected item 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?

Single sentence is concise but contains '[UNIFIED]' metadata noise. However, extreme brevity is inappropriate given zero schema documentation - conciseness becomes under-specification.

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?

Completely inadequate for a 3-parameter mutation tool with no annotations, no output schema, and 0% parameter description coverage. Missing: parameter details, error behavior, return values, and format specifications.

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. Description fails to compensate: 'site' (URL or name?), 'collection' (identifier format?), and 'data' (array of objects with what structure?) are completely undocumented. No examples or constraints provided.

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 basic action (import) and target (items into collection) but includes metadata noise '[UNIFIED]' prefix. Weak distinction from sibling directus_create_items - both handle multiple items but the critical difference (import vs create semantics) is unexplained.

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 no guidance on when to use this versus directus_create_items or directus_import_file_url. No mention of prerequisites, data format requirements, or bulk operation limits.

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