superset_user_get_current

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the non-obvious two-path implementation (/api/v1/me/ first, JWT 'sub' claim decode + /security/users/{id} fallback) and that some instances restrict the primary endpoint. It stops short of stating authentication requirements explicitly, rate limits, or failure behavior when neither endpoint works.

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 purpose is front-loaded in the first sentence, with the fallback mechanics relegated to follow-up lines that an agent only needs if the call fails. Every sentence earns its place; nothing is padded.

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 with no output schema, the description covers purpose, retrieval mechanics, and the rough return shape ('a dictionary with user profile data'). The return shape is only loosely characterized — no field list or error semantics — but that is a minor gap for this simple tool.

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 per the baseline the schema cannot be a source of semantic gaps. The description correctly implies the user identity is derived from the caller's token rather than supplied as input.

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 precise verb (Get) and a precisely scoped resource (information about the currently authenticated user), which cleanly separates it from siblings like superset_user_get_roles or superset_auth_authenticate_user. No ambiguity about whose profile is returned.

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?

Usage is only implied: an agent can infer this is the tool for 'who am I / my profile' questions, but the description never states when to prefer it over superset_auth_check_token_validity or superset_user_get_roles, nor does it note any prerequisite beyond implicit authentication. Adequate context, but no explicit routing guidance.

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