Sends UTF-8 plain text messages to a configured WeCom group chat bot, validates the 2048-byte limit, and returns platform acceptance or error status.
Send UTF-8 plain text (max 2048 bytes) to the configured WeCom group. Requires explicit user intent to send. Accepted does not mean read. Never automatically retry unknown delivery.
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds substantial context beyond the annotations: explicit user intent, UTF-8 plain text limit, the distinction between accepted and read, and a no-auto-retry rule for unknown delivery. These are important operational cautions for a destructive, non-idempotent send operation.
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?
Four short sentences, all front-loaded and purposeful. Each sentence adds either purpose, constraint, or safety guidance without repetition.
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 one-parameter send tool with no output schema, the description covers the operation, input constraints, required user intent, and key delivery semantics. Annotations already cover read-only, destructive, openness, and idempotency traits, so little is missing.
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 schema has one undocumented content parameter at 0% description coverage. The description compensates by defining the payload format as UTF-8 plain text with a maximum size, which is the key semantic detail an agent needs.
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: send plain text to the configured WeCom group. It also includes key constraints such as UTF-8 and 2048-byte maximum, so the agent can identify the operation immediately.
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?
Gives a clear usage condition: explicit user intent is required before sending. It does not need to route to a sibling because none are listed, but it could be slightly stronger by specifying when not to use it beyond intent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.