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

Well beyond the annotations (destructive, openWorld, non-idempotent), it discloses that messages are attributed to the caller's name, cannot be deleted through Cotlet, require per-message confirmation by default (switchable off for this tool), and wait on the owner's approval. It also names two concrete refusal conditions (self-message, group level limits).

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?

The first two sentences say the same thing twice ('starting a conversation if needed' / 'starts a conversation if there is none yet'), which is wasted space. The remaining sentences are dense and earn their place, but the redundant opening hurts front-loading.

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 mutation tool with no output schema, it covers the confirmation/approval flow, attribution, irreversibility, and group resolution — enough to call it correctly. It does not say what the tool returns or blocks on after approval, a minor residual gap.

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 already 100%, so the baseline is 3. The description adds real value on `group` by explaining the fallback resolution order and on `member_id` by tying it to list_members / list_conversations, though it adds nothing for `body`.

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 first sentence names a specific verb (send), resource (direct message in Skool Chat), and target (a member), plus the side effect of starting a conversation. It is distinguishable from siblings like comment_on_post or list_conversations, but it never explicitly contrasts itself with them, so it stops short of a 5.

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?

The description gives operational context: pass a group or accept the first group Skool accepts, self-messages are refused, and groups may restrict chat by level. However, it never says when to prefer this over comment_on_post or set_auto_dm-driven messaging, leaving usage selection implied rather than guided.

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