Gửi thử vào nhóm Zalo

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

No annotations are present, so the description carries the full disclosure burden. It does disclose two behavioral constraints: the bot must exist in the group and Markdown will not be parsed. However, it does not mention that this sends a real visible message to the group or what success/failure looks like.

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?

One compact sentence delivers action first, then prerequisite and rationale. There is no filler, no repetition of schema content, and every clause earns its place.

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 single-parameter test tool, the essential context is present: what it does, the required group precondition, and why only plain text is supported. Missing return-value or side-effect detail is a minor gap given the simple schema and absent output schema.

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?

Schema description coverage is 100%; the id parameter is already documented as the MONA Pay Zalo group configuration ID (UUIDv6). The description adds no parameter-level information, so the baseline 3 applies.

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 states a specific action: send a test plain-text message to a Zalo group ('Gửi tin thử text thuần'), and the second clause confirms the group context. 'Thử' plus the text-only constraint clearly differentiates it from the Zalo group create/update/delete/list/log siblings.

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?

It provides actionable usage context: the target group must contain the Gấu Mona bot, and the message must be plain text because Zalo does not render Markdown. It does not explicitly name alternative tools, but there is no direct sibling for sending a test Zalo message, so the prerequisite is sufficient guidance.

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