Send Discord DM

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

Discloses key behaviors: mentions always disabled, server sharing requirement, opt-in policy, and dryRun flag. No annotations exist, so description carries full burden. Does not cover rate limits or authentication, but sufficient for safe usage.

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?

Five sentences efficiently cover purpose, parameters, constraints, and policy. Front-loaded with core purpose, no redundancy. Every sentence is informative.

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 all critical aspects: identification, message types, constraints, and opt-in policy. Missing description of return value or error handling beyond error 50007, but sufficient for a direct message tool with 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?

Schema coverage is 100%, baseline 3. Description adds value by explaining usage patterns (e.g., 'Supply content for a plain message, and/or escalation'), resolving githubLogin via mapping, and detailing dryRun behavior. Escalation object purpose is clarified.

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 direct message to a Discord user via a bot, specifying REST-only and no gateway. It distinguishes between plain messages and structured escalation requests, making the purpose unambiguous.

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?

Provides clear usage context: when to DM (for opted-in users), how to identify recipients (discordUserId or githubLogin), and prerequisites (bot must share server). Lacks explicit 'when not to use' but given no siblings, this is adequate.

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