send_dm_to_group

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

Without annotations, the description carries full burden. It discloses privacy ('PRIVATE message') and anti-spam consequences, but does not detail rate limits, permissions, or return behavior. Output schema exists but is not described.

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?

Description is concise with a main line, a focused warning, and parameter list. No redundant sentences, but the warning could be integrated more tightly.

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 purpose, usage warnings, and parameter details adequately. With output schema present, return value explanation is unnecessary. However, could mention that this is a mutating action.

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 coverage is 0%, so description compensates well. It explains group_id ('conversation ID'), text ('required, must not be empty'), and media_id ('Optional media ID to attach'), adding constraints beyond schema.

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 'Send a direct message to a group conversation,' with a specific verb, resource, and scope. It differentiates from sibling tools like 'send_dm' (individual DM) and 'delete_dm'.

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 warns 'Do not bulk-call' and explains anti-spam risks, providing clear context when not to use. It implies usage for individual group DMs, but does not explicitly compare to 'send_dm'.

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