Get current user

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds context by specifying that the user is the one who owns the API token, clarifying the relationship between the token and the returned user. No contradiction with annotations.

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 first sentence is concise and informative. The second sentence, 'Operation: GetCurrentUser,' is redundant since it repeats the tool name/operation. While not harmful, it adds little value. Overall the description is short and front-loaded.

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 tool with no output schema, the description sufficiently covers the tool's function. It could mention the fields returned, but for a simple user object this is often implied. The description is adequate given the tool's simplicity.

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, and the schema is empty with 100% coverage. There is nothing for the description to explain about parameters. The baseline of 4 for 0 params applies, and the description appropriately says nothing.

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 tool's purpose: 'Get the user that owns the API token.' This is a specific verb (get) and resource (user determined by token ownership), which distinguishes it from other get_* tools like get_customer or get_product. The tool's name and title reinforce its meaning.

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 implies usage context: use this tool to retrieve the authenticated user's information. It does not explicitly mention alternatives or situations to avoid, but because it targets the current user only, there is little ambiguity. The unique scope makes it clear that this is the tool for the current user.

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