directus_create_item

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

No annotations provided, so description carries full burden. 'Create' implies write operation but description lacks details on authentication requirements, validation behavior, or side effects. '[UNIFIED]' tag is opaque and unexplained.

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 '[UNIFIED]' prefix appears to be leaked metadata or tags that doesn't earn its place. Front-loading structure is acceptable but content is insufficient.

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?

Inadequate for a mutation tool with nested object parameters and no output schema. Missing critical context: relationship to sibling bulk tool, parameter semantics, return behavior, and the meaning of the unified/site architecture.

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 with 4 parameters (including complex nested 'data' object). Description mentions 'any collection' implying the collection parameter but completely fails to explain 'site', 'data', or 'fields' parameters or their expected formats.

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 verb ('Create') and resource ('item') but fails to distinguish from sibling tool 'directus_create_items' (bulk variant). The '[UNIFIED]' prefix is unexplained metadata that doesn't clarify purpose.

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-item tool versus the bulk 'directus_create_items' alternative. No mention of required permissions, site configuration, or prerequisites for the 'site' parameter.

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