get_user_info

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

Annotations already indicate a safe, read-only operation. The description adds no behavioral context, such as error handling, response format, or any side effects. With the burden low due to annotations, the description still fails to provide extra insight.

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 description is a single short sentence, front-loading the purpose. No wasted words, though its brevity may sacrifice clarity for non-Chinese speakers. It is appropriately sized for a simple tool.

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?

Given the existence of an output schema, the description need not detail return values. However, the tool's role among many user-focused siblings is not clarified, and the openWorldHint is not explained. The description is adequate but incomplete for optimal tool selection.

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 input schema already describes the 'username' parameter as '用户名/ID' with 100% coverage. The description '获取用户信息' does not add any additional meaning or constraints beyond what the schema provides, meeting the baseline for high schema coverage.

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?

The description '获取用户信息' clearly states the tool returns user information for a given username. It is a specific verb and resource, but it does not specify the scope of returned data, nor does it differentiate from similar tools like get_me_info or other user-specific tools.

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?

No guidance is provided on when to use this tool versus alternatives like get_me_info, get_user_avatar, or get_user_collections. The agent is left to infer based on the tool name and parameters.

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