get-current-user

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The phrase 'currently authenticated' hints at dependency on authentication state, but it does not specify what happens when no user is logged in, whether the operation is read-only, or what the return value looks like. This is a minimal, nearly tautological description that adds little beyond the tool name.

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 a single, clear sentence that immediately conveys the tool's purpose. It is appropriately sized for a simple zero-parameter operation, with no wasted words or redundant information.

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?

Given the tool's simplicity (0 params, no output schema), the description is a minimal viable statement. However, it lacks details about return value (e.g., full user object or just ID) and behavior when unauthenticated, which an agent might need for correct invocation. The absence of these details makes it only partially complete for a real-world usage context.

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?

The tool has zero parameters, so the schema fully covers parameter semantics, and no additional parameter explanation is needed. The baseline for 0-parameter tools is 4, and the description does not introduce any unnecessary parameter details.

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 uses a specific verb 'get' and identifies a clear resource: 'the currently authenticated user.' This clearly distinguishes it from sibling tools like get-object or query-users, which target other resources or require parameters. It unambiguously states what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives, such as query-users or get-object for retrieving specific users. There is no mention of prerequisites like being logged in, nor any exclusions. The context signals show a large sibling list, but the description offers no comparative advice.

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