getCurrentUser

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

Without annotations, the description carries the full burden of behavioral disclosure. It only restates the action and gives the endpoint, but does not explain the return format, error behavior (e.g., unauthenticated requests), or that it is a read-only operation. The 'get' verb and 'GET' method hint at safety, but deeper details are missing.

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, front-loaded sentence that conveys both the action and endpoint. It is maximally concise without any wasted words, making it easy to parse and understand quickly.

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 tool with no output schema, the description is relatively complete. It tells the agent exactly what to expect: it gets the current authenticated user. However, it could be improved by noting the return type (e.g., 'returns the user object') or any authentication prerequisites, but these are largely implied by the tool's name and endpoint.

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 is nothing to add. The schema coverage is 100% by virtue of having no params. The description does not need to explain any parameters, and the baseline for zero-param tools is 4, which is appropriate here.

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 clearly states the function: 'Get the current authenticated user' with the explicit endpoint '(GET /me)'. The verb 'Get' is specific, and 'current authenticated user' distinguishes it from sibling tools like getUser (which implies fetching a user by ID) and listUsers (which lists multiple users).

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 explicit guidance on when to use this tool versus alternatives. It does not mention that this is the appropriate tool when you need the current authenticated user's information without providing an ID, nor does it exclude alternatives like getIdentity or getUser. The context is implied by the name but not articulated.

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