wechat_send_text

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 states that the message is plain text and the recipient must be known, but it does not disclose side effects, failure modes, whether the send is synchronous, or what happens if the user is unknown. This lack of behavioral detail is a significant gap.

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, front-loaded sentence that conveys the core action and constraint without any wasted words. It is efficient and easy to parse.

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?

The tool is simple with well-documented parameters, but the description lacks behavioral context such as error handling, return values, and any side effects. The known-user constraint provides some context, but overall the description is minimally complete for a send operation.

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 provides comprehensive descriptions for both parameters (UTF-8 encoding, paragraph splitting, ID format). The tool description adds no additional parameter meaning, and with 100% schema coverage the baseline of 3 is appropriate.

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 sends a plain text message to a specific userId, distinguishing it from sibling tools like wechat_send_image, wechat_send_file, and wechat_send_url. The constraint "must be a known user" adds specificity to the target.

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 this tool is for sending text messages, but it does not explicitly mention alternatives or when not to use it. The precondition of a known user is mentioned, but no guidance is given on how to verify or handle unknown users.

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