get_current_user

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

The description is semantically transparent for a simple read operation: 'Get' implies no side effects, and 'currently authenticated' ties the behavior to the caller's auth session. However, it does not disclose return shape, possible authentication errors, or other runtime behavior, and there are no annotations to fill that gap.

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 with no filler, redundancy, or irrelevant detail. It earns its place and is as concise as possible for an MCP description.

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, no-option read operation, the description is nearly complete: it identifies the resource and the authentication scope, which is sufficient for selection and invocation. The main gap is the lack of any return-value description, but the low complexity and absence of configuration reduce the need.

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 input schema is an empty object with zero parameters, so there are no parameter semantics for the description to clarify. The 0-parameter baseline of 4 applies; no additional parameter documentation is needed.

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 an unambiguous verb ('Get'), a specific resource ('user'), and a scope qualifier ('currently authenticated') that clearly differentiates it from sibling tools such as get_user and list_users. There is no ambiguity about what this 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 does not explicitly indicate when to use this tool over alternatives like get_user or list_users, and it names no exclusions or decision rules. The phrase 'currently authenticated' implies session context, but that is left to inference.

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