get_current_user

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

No annotations are provided, so the description carries the full disclosure burden. While 'authenticated' hints at auth requirements, the description fails to specify what 'details' are returned (fields, structure), whether the data is cached, or other behavioral traits like idempotency.

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?

Single sentence is appropriately front-loaded with the action. Efficient length for a zero-parameter tool, though 'details' is slightly vague and could be more specific about what user properties are fetched.

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?

Adequate for a simple identity retrieval tool, but lacks return value documentation needed given the absence of an output schema. Does not mention what user attributes (ID, email, permissions) are included in the response.

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?

Input schema has zero parameters, establishing the baseline score of 4 per the rubric. The description correctly implies no inputs are needed beyond the implicit authentication context.

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 clear verb ('Get') and specific resource ('details of the current authenticated user'). The term 'current' implicitly distinguishes it from sibling tools 'get_user' and 'get_users', though it doesn't explicitly contrast them.

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?

Provides no guidance on when to use this versus alternatives like 'get_user' (e.g., when you don't know the user ID) or when it should be invoked (e.g., at session start). Contains no 'when-not-to' or prerequisite information.

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