Get Current User

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' strongly implies a read-only operation with no side effects, and listing profile fields is helpful, but the description does not explicitly state read-only behavior, auth requirements beyond 'authenticated,' or any other behavioral traits. Still, for a simple getter this level is adequate.

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 that communicates purpose and output fields with zero wasted words. It is optimally concise for a simple no-parameter tool.

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 has no parameters gagliardetto and an output schema exists, the description fully covers what an agent needs: what the tool does, whose profile it returns, and which fields are included. No significant information is missing.

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 are no parameter semantics to document. The baseline for a zero-parameter tool is 4, and the description adds value by specifying the returned profile fields, which is sufficient given the empty input schema.

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 states a specific verb ('Get'), a clear resource ('current authenticated user's profile'), and enumerates the returned fields (id, name, email, picture). This distinguishes it from sibling get_user by emphasizing the current authenticated user, and it is immediately clear 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 phrase 'current authenticated user' provides clear context for when to use the tool: when you need the profile of the logged-in user. However, it does not explicitly contrast with sibling get_user or state when not to use this tool, leaving the comparison to the agent's inference.

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