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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety bar is lower; the description still adds two non-obvious behaviors: it auto-creates a conversation and it 'Waits for the owner's approval.' It does not explain why the action is destructive or whether a message can be retracted, but the approval gate is genuine added value.

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?

Two sentences, zero waste, with the core action front-loaded and the behavioral caveat second. Nothing is repeated from the title or schema.

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 3-param mutation with no output schema, the description covers what it does, the auto-conversation behavior, and the approval gate. The main omission is return semantics: an agent can't tell whether the call resolves immediately, returns a pending-approval status, or fails when approval is denied.

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 100% and the schema already documents all three parameters, including where member_id comes from and the group default. The description adds no syntax, format, or constraint detail beyond that, 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?

States a specific verb and resource ('Send a direct message in Skool Chat to a member') plus scope details (direct message, not a post comment; conversation auto-created). It is clearly distinct from most siblings, though it never names the nearest neighbor (comment_on_post) or set_auto_dm to sharpen the boundary.

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?

'starting a conversation if needed' implies when to use it over get_conversation/list_conversations, but only by implication. There is no explicit when-to-use/when-not guidance, no mention of alternatives for reaching members, and no prerequisites beyond the approval note.

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