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 one meaningful fact—identity is derived from the token, requiring no user ID—but says nothing about the detail enum's effect, pagination behavior, or the offset-based continuation the schema implies.

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 tightly worded sentence, front-loaded with the core action, with zero filler. It is efficient, though its brevity borders on under-specification for a tool offering detail levels and offset continuation.

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?

An output schema exists, so return values needn't be described, and the annotations cover safety. However, the detail parameter's semantics and the offset-based continuation strategy remain unexplained, leaving an agent to guess how to request full versus summary output.

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?

Schema description coverage is 67%, with the two offset parameters well described in the schema but the detail enum (summary vs full) undocumented anywhere. The description contributes no parameter information, so it neither compensates for the gap nor adds value; the schema does most of the work.

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?

States a specific verb (read) and resource (the user authenticated by the API token), which is precise scope. It effectively distinguishes itself from siblings like list_users or get_user_timelogs by implying token-identity rather than an ID lookup, though it never names an alternative explicitly.

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?

There is no when-to-use guidance, no conditionality, and no named alternative. The agent must infer that this is for retrieving the caller's own identity versus consulting list_users for other users; nothing in the text makes that explicit.

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