send_message

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

Discloses rate-limiting (60s dedup window), blocking behavior on reply, and reply content. Annotations are minimal, so description adds significant context beyond readOnlyHint and destructiveHint.

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?

Well-structured with core function, example, behavior, and alternatives grouped. Slightly verbose but every sentence adds value.

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?

Covers usage, behavior, splitting, and alternatives. Lacks error cases and full reply format, but is sufficient for a messaging tool given 7 params and no 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?

With 0% schema coverage, the description partially compensates by explaining content splitting and wait_reply behavior, but lacks explicit description for all parameters (e.g., num_chunks is only indirectly hinted).

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 text message to a QQ group or friend with optional reply waiting. It distinguishes from siblings by naming alternative tools for images, audio, files, and standalone waiting.

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?

Explicitly provides when to use alternatives (e.g., send_image for images) and describes message splitting technique with </分段> tags. This guides the agent to choose correctly.

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