directus_update_current_user

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. 'Update' implies mutation, but fails to specify if partial updates are supported, what happens to omitted fields, side effects, or permission requirements beyond implied authentication.

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 with efficient structure. The '[UNIFIED]' prefix appears to be metadata noise, but the core description is appropriately front-loaded and free of redundancy.

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 zero schema documentation and no output schema. The nested 'data' object (additionalProperties: true) particularly requires explanation given the high flexibility and zero schema coverage, which is not addressed.

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% (neither 'site' nor 'data' have descriptions). The description mentions 'profile' which weakly hints at the purpose of the 'data' object, but provides no explanation for the 'site' parameter or what structure/data types are expected in the profile update.

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 specific resource 'currently authenticated user's profile'. Distinguishes from sibling 'directus_update_user' (which updates any user) by specifying 'current' user, though 'profile' remains somewhat vague regarding which fields are updateable.

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?

Lacks explicit guidance on when to use versus alternatives. While 'currently authenticated' implies self-service usage, it does not explicitly state when to prefer 'directus_update_user' (for other users) or note prerequisite authentication requirements.

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