directus_create_collection

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

No annotations provided, so description carries full disclosure burden. Fails to indicate whether this operation is reversible, idempotent, requires specific permissions, or what happens when the collection already exists. Does not disclose that this modifies database schema.

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 appropriately brief, but the '[UNIFIED]' prefix wastes tokens without aiding agent comprehension. The parenthetical '(table)' adds useful clarity.

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?

Severely inadequate for a database schema creation tool with 5 undocumented parameters and no output schema. Lacks explanations for parameter relationships, error states, return values, or prerequisite conditions.

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. Despite 5 parameters (including complex ones like 'schema' and 'fields' which are ambiguous in this context), the description provides zero parameter guidance. 'Site' and 'collection' are undocumented, and the data format/structure for optional string parameters (meta, schema, fields) is unexplained.

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), resource (collection/table), and system context (Directus), distinguishing it from sibling appwrite_create_collection. However, the '[UNIFIED]' prefix adds noise without value, and it doesn't clarify how a 'collection' differs from 'field' or 'item' siblings within Directus.

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 versus alternatives like directus_update_collection, prerequisites for use (admin rights), or when creation might fail (duplicate names).

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