directus_update_item

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

No annotations provided, so description carries full burden. Does not disclose mutation side effects, whether updates are partial (PATCH) or full replacement (PUT), what gets returned on success/failure, or any permission requirements. '[UNIFIED]' tag is 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 concise but undersized for tool complexity (5 parameters, nested objects, no output schema). '[UNIFIED]' prefix wastes valuable descriptive space without adding agent-usable context.

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 5-parameter mutation tool with zero schema documentation and no output schema. Lacks explanation of return values, error modes, relationship to Directus collections, and parameter interdependencies (site+collection+id).

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, requiring heavy compensation. Description only implicitly covers 'id' ('by ID') and hints at 'data' ('Update'). Completely silent on 'site' (instance selection), 'collection' scope, and 'fields' parameter purpose, leaving critical 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?

States basic action 'Update' and resource 'item' with scoping 'by ID', but fails to distinguish from sibling 'directus_update_items' (bulk) or clarify what constitutes an 'item' in Directus context. The '[UNIFIED]' prefix is metadata noise that doesn't aid understanding.

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 singular update vs the bulk 'directus_update_items' alternative. No mention of prerequisites (item must exist), partial vs full update semantics, or error conditions (e.g., non-existent ID).

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