directus_update_collection

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

No annotations provided, yet description fails to disclose mutation behavior, partial update semantics ( PATCH vs PUT style for the meta object), or that missing keys in 'meta' preserve existing values. No mention of authentication requirements or side effects.

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 and front-loaded, but '[UNIFIED]' prefix is implementation noise that wastes space without aiding agent decision-making. Appropriate length for the content provided, though content is insufficient given schema gaps.

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 incomplete given zero annotations, zero schema descriptions, and no output schema. For a mutation tool affecting 3 parameters, description omits critical context: parameter formats, valid meta fields, and return behavior.

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, description fails to compensate. Does not explain 'site' (instance identifier), 'collection' (collection key/name), or 'meta' structure (free-form object containing icon, color, note, etc.). Only vague linkage between 'meta information' text and 'meta' parameter name.

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?

Clear verb 'Update' and resource 'collection meta information'. Distinguishes from siblings like create_collection, delete_collection, and get_collection by specifying 'meta' scope. However, 'meta information' remains vague regarding Directus-specific concepts (schema metadata vs. display metadata).

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 versus directus_update_field, directus_schema_apply, or other mutation tools. No mention of prerequisites (admin permissions) or preconditions (collection must exist).

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