directus_get_user

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

With no annotations provided, the description carries full behavioral disclosure burden but fails to specify return value structure, error handling (e.g., 404 for invalid ID), permission requirements, or whether sensitive fields like passwords/tokens are returned. Only states the obvious read operation.

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?

Extremely brief (one sentence plus metadata tag). The '[UNIFIED]' prefix appears to be implementation metadata leakage that adds no value. While not verbose, the brevade is excessive given the complete lack of schema documentation and output schema.

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 user lookup tool with no output schema and zero parameter documentation. Missing: parameter descriptions (especially 'site'), return value specification, error conditions, and permission context. The single sentence is insufficient compensation for missing structured metadata.

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?

Critical gap: schema has 0% description coverage for both 'site' and 'id' parameters. Description mentions 'by ID' implying the 'id' parameter accepts user identifiers, but completely omits explanation of the 'site' parameter (instance name? site ID? URL?), leaving agents guessing how to populate required parameters.

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 specific action (Get) and resource (user details) with key constraint (by ID). The '[UNIFIED]' prefix is noise but doesn't obscure meaning. Distinguishes from CRUD siblings (create/update/delete) and implies distinction from list_users via singular 'user' and ID requirement, though explicit differentiation from get_current_user is absent.

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_list_users (for querying multiple users) or directus_get_current_user (for the authenticated user). No prerequisites or permission requirements mentioned despite the tool likely requiring admin or specific role access to fetch arbitrary user details.

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