directus_update_folder

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

With no annotations provided, the description carries full burden but only indicates mutation via 'Update'. It fails to disclose whether changing the parent moves subfolders/contents, if the operation is idempotent, or error conditions (e.g., circular parent references).

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?

The description is brief (one sentence) but front-loaded with the non-descriptive '[UNIFIED]' tag. The core message is efficient but excessively minimal given the lack of schema documentation.

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 an update operation with zero schema coverage and no output schema. The description mentions updatable fields but doesn't explain parameter relationships (e.g., that 'id' specifies which folder to update) or return values.

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. While the description mentions 'name or parent' (suggesting these go in the 'data' object), it completely omits explanation of the 'site' and 'id' parameters, leaving the agent to infer these identify the target folder and instance.

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?

The description clearly states the tool updates folder 'name or parent', identifying both the resource (folder) and specific updatable fields. However, the '[UNIFIED]' prefix is metadata noise that doesn't help the agent understand functionality.

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 provided on when to use this versus directus_create_folder or directus_delete_folder. No mention of prerequisites like folder existence checks or permissions required to move folders between parents.

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