get_current_user

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

There are no annotations to rely on, and the description does not disclose any behavioral aspects beyond the name, such as authentication requirements, potential errors, or side effects. It merely restates the function without adding operational context.

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, lean sentence that conveys the core purpose efficiently. No unnecessary words or redundancy, making it a model of 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?

For a simple, parameterless tool with an output schema, the description is essentially complete. However, it could marginally benefit from a hint about when to use this over related 'get' tools, but given the presence of an output schema, it falls just short of perfect.

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 baseline is 4. The description does not add parameter-level details, but none are needed. The schema and empty property set already fully cover this aspect.

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 clear verb ('Return') and a specific resource ('currently authenticated user's profile'). It unambiguously differentiates from sibling tools like 'get_my_project_access' by explicitly scoping to the current user's profile.

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 is provided on when to use this tool versus alternatives, no exclusions, and no context about scenarios where it is appropriate. The description only states what it does, leaving the agent without decision-making help.

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