directus_get_current_user

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

No annotations provided, so description carries full disclosure burden. 'Authenticated' hints at auth requirements, but lacks specifics on error behavior, returned fields, or caching. Does not mention that 'site' parameter likely determines which Directus instance to query.

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), but the '[UNIFIED]' prefix appears to be metadata noise rather than descriptive content. Given the lack of parameter documentation and behavioral details, this brevity constitutes under-specification rather than efficient conciseness.

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?

With zero schema coverage, no output schema, and a single required parameter, the description should minimally explain the parameter's purpose and expected return structure. It provides neither, leaving critical gaps for agent invocation.

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% (the 'site' parameter is undocumented in schema). Description completely omits parameter explanation; with 0% coverage, the description must compensate by explaining what 'site' represents (URL? ID? Name?), which it fails to do.

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 a clear verb ('Get') and resource ('currently authenticated user'). The term 'current' implicitly distinguishes it from sibling directus_get_user (which likely retrieves arbitrary users by ID), though explicit differentiation would strengthen this.

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_get_user or directus_update_current_user. Does not mention prerequisites (e.g., valid auth token required) or failure modes (e.g., unauthenticated requests).

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