get_current_user

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

Beyond readOnlyHint=true, the description discloses that identity is derived from the AccessKey rather than a parameter, and that setting YUNXIAO_USER_NAME triggers strict validation — an important failure mode an agent would otherwise not anticipate. It does not discuss scoping to the 'current project' beyond mentioning it, but the added context is substantive.

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?

Two compact sentences front-load the core purpose and then add the comparison hint and validation caveat. Every clause carries information, though the YUNXIAO_USER_NAME clause is terse enough to be slightly opaque.

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?

With an output schema present and no parameters, the description only needed to explain what identity is resolved and how the result is used, which it does. The only gap is the absence of guidance on the 'current project' context and how that scope is determined.

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, but the description spends words on 'identifier' and 'assignedTo,' which are return/comparison fields rather than inputs. It adds no parameter meaning because there are none to clarify.

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 and resource: retrieve the Yunxiao user bound to the current AccessKey plus that user's member ID in the current project. This clearly separates it from siblings like list_project_members (which enumerates members) and get_project, 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?

Implies the usage context by saying the returned identifier can be compared against assignedTo, which points at filtering work items by current user, but it never states when to call this versus list_project_members or get_project. The YUNXIAO_USER_NAME note hints at a validation mode but is not framed as a precondition for choosing the tool.

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