Get current user

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description aligns by describing a read-only profile retrieval. It adds useful context not present in annotations: the operation concerns the authenticated user, implying authentication is required and that this is a safe, non-mutating call.

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?

A single, front-loaded sentence conveys the action, resource, and scope with no unnecessary words. It is exactly as concise as the tool's simplicity allows.

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?

For a zero-parameter, read-only tool, the description is largely complete: it names the resource and the authentication context. A small gap is that it does not reference tribeunal_get_user as the alternative for non-current users, and it does not enumerate profile fields, but neither is essential for correct 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?

The tool has zero parameters, so there is nothing for the description to explain. The empty schema and parameter count fully align with the description, making the baseline of 4 appropriate.

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 a specific verb ('Get') and resource ('profile information for the currently authenticated user'), which distinguishes it from the sibling tribeunal_get_user that likely targets a different user. The 'currently authenticated' qualifier removes ambiguity about which user is being accessed.

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 makes the usage context explicit: use this tool when you need profile data for the currently authenticated user. It does not explicitly mention tribeunal_get_user as an alternative for other users, but the phrase 'currently authenticated' strongly implies the intended scope.

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