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. It reveals a nontrivial behavior: 'Logs in automatically if needed,' which is important for an agent to anticipate side effects. It also implies a read-only operation via 'Get,' though it does not explicitly rule out modifying state or describe login side-effect details.

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 two tight sentences: the first front-loads the purpose and return contents, and the second adds the one essential behavioral caveat about automatic login. Every word earns its place with no redundancy or filler.

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 parameterless, read-style tool with no output schema, this description is complete: it names the target entity, the available data fields, and the login behavior an agent must know before calling. Nothing essential is missing for correct invocation or interpretation of results.

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?

There are zero parameters, so the input schema already covers everything. The description appropriately adds no parameter documentation because none is needed, which matches the schema coverage of 100%. A baseline of 4 is appropriate for a parameterless tool.

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 starts with a specific verb and resource: 'Get the currently logged-in NodeLoc user' and lists the exact returned fields (id, username, trust level, unread notification counts). This clearly distinguishes it from sibling tools like get_user_profile or get_user_summary, which target other users rather than the active session.

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 phrase 'currently logged-in NodeLoc user' provides clear context for when to call this tool: when the agent needs data about the authenticated user. The mention that it logs in automatically also signals that no separate authentication step is required. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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