wechat_self_info

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

No annotations are provided, so the description carries the burden of conveying behavior. The verb '获取' indicates a read-like operation, but the description does not disclose potential side effects, authentication requirements, rate limits, or return format. It adds minimal behavioral depth beyond the action itself, which is acceptable for a simple getter but not fully transparent.

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 concise sentence that directly states the tool's purpose. It is front-loaded with the verb and resource, contains no redundant information, and is appropriately sized for a tool with no parameters.

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 no output schema and no annotations, the description is the only source of information about the return value. It simply says '个人信息' (personal information), which is vague and does not specify what fields (e.g., nickname, avatar, ID) will be returned. Given the low complexity (0 params), this is adequate but leaves room for richer context.

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 has zero parameters, and the schema coverage is 100% (trivially). The description adds semantic value by clarifying scope ('当前登录' - currently logged in), which explains why no parameters are needed. Baseline for 0 params is 4, and the description satisfies this without needing to explain parameter syntax.

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 action ('获取' - get) and the specific resource ('当前登录微信账号的个人信息' - personal information of the currently logged-in WeChat account). This distinguishes it from siblings like wechat_contact_info (which retrieves other contacts' info) and wechat_status (which retrieves status).

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?

The description implies that this tool is used to fetch the current user's own profile information, which provides some context. However, it does not explicitly mention when to use it over alternatives, nor does it state any exclusions or prerequisites. Usage guidance is purely implicit.

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