conf_get_current_user

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond them: it does not say what happens when no credentials exist (error vs. unauthenticated payload) or what the response looks like, so it contributes no behavioral context of its own.

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?

It is a single front-loaded phrase with zero waste, which is good, but the brevity crosses into under-specification: three words omit any usage context or return information and would have benefited from one clarifying sentence.

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 identity tool with no output schema, the description is minimally sufficient, and annotations carry the safety profile. It is still incomplete on the two things an agent cannot infer: the returned fields and behavior under missing or expired authentication.

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 takes zero parameters, so there are no parameter semantics that the description must explain. Baseline for a parameterless tool applies.

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?

"Get authenticated user" names a specific verb and resource, and it is distinguishable from the nearby conf_browser_auth_status sibling, which concerns auth state rather than identity. It stops short of naming that sibling or saying what the returned user record contains.

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 use case (identify who the current credentials belong to) is strongly implied, but there is no explicit when-to-use, no when-not, and no routing to alternatives such as conf_browser_auth_status when the agent only needs to know whether it is logged in.

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