get_current_user

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

The description indicates the returned fields (id, email, default workspace) and implies a read-only operation. However, with no annotations, it lacks details on authentication requirements, error conditions (e.g., not logged in), or any side effects. Behavior is partially disclosed but not thoroughly.

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, concise sentence that front-loads the action and resource. No unnecessary words. Every part contributes value.

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 zero parameters and no output schema, the description provides a clear picture of what the tool returns. It does not explain return format in detail, but for a simple info retrieval tool, it is adequate. Could mention that it returns only the logged-in user, not a specific user.

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 zero parameters, so schema coverage is 100%. The description does not add information about parameters because there are none. With 0 parameters, the baseline is 4, and the description meets that expectation.

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 verb 'Get' and the resource 'currently logged-in user's info', specifying the exact fields returned (id, email, default workspace). This distinguishes it from siblings like list_users (multiple users) and get_user_member_profile (likely for a different user).

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 when not to use it or provide context for selection among siblings like list_users or get_user_member_profile.

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