get_logged_in_user

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

No annotations are provided, so the description carries the full burden. It only drops the bare keyword 'read-only' and never states the auth requirement (must be logged in), what fields the profile returns, or error behavior for an unauthenticated call.

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 core phrase 'Get user self' is front-loaded, but the bulk of the text is a keyword dump repeating the same concept in eight phrasings ('get/fetch/read/retrieve/view/show user self') plus generic tokens. That padding does not earn its place.

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 tool with no output schema, the description is minimally adequate: it conveys that the current user's own record is returned. It does not describe the returned profile shape or any auth precondition, leaving gaps an agent would prefer filled.

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 takes zero parameters, so the baseline is 4. There are no inputs for the description to clarify, and the schema trivially matches.

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+resource: 'Get user self', backed by the HTTP route [GET /api/users/self]. It is understandable apart from most siblings, though it never explicitly separates itself from update_user or the more specific get_logged_in_user_* variants.

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 or mention of any alternative. With siblings like get_logged_in_user_ratings, get_logged_in_user_favorites, and update_user, the agent gets no help deciding this is the base profile fetch.

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