getCurrentUser

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

No annotations are present, so the description carries full burden. 'Show current user' implies a read operation, but it fails to disclose behavioral traits such as authentication requirements, idempotency, or potential side effects. It does not mention what happens if the user is not authenticated.

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 only three words, which is concise but under-informative. It lacks necessary details about parameters and behavior. A good description should be concise yet complete; this is merely abbreviated without serving its function.

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 two parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how to use the parameters, or any authentication context. The agent cannot effectively invoke this tool based on the description alone.

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 input schema has two parameters (pathParams.format and queryParams.include) with no descriptions (0% schema coverage). The description does not explain any parameter meaning, default values, or why they are required. The agent cannot understand how to use parameters from the description alone.

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 'Show current user' clearly indicates the verb (show) and resource (current user), which distinguishes it from siblings like 'getUser' (which gets a specific user by ID) and 'getMyAccount' (which might be similar but is separate). However, it does not elaborate on what 'show' entails, so sibling differentiation is implicit but not explicit.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or scenarios where 'getUser' or 'getMyAccount' would be more appropriate. The agent receives no context for tool selection.

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