discord_open_dm

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

No annotations are provided, so the description must fully disclose behavioral traits. It hints at idempotency with 'open (or fetch)' but does not state whether it creates a new DM channel if one does not exist or errors. It also omits required permissions (e.g., must be friends? mutual guilds?) and side effects. This leaves ambiguity for a mutation-like tool.

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 description is a single 12-word sentence, extremely concise. It front-loads the action and directly states the output. No extraneous information; every word is purposeful.

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?

Given the tool's simplicity (1 parameter, no output schema), the description covers purpose and return value. However, it lacks details on whether the operation is idempotent, what happens if the user does not exist, and any side effects. For a tool with no annotations, these gaps reduce completeness to a minimum viable level.

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?

The sole parameter 'userId' is described only as 'with a user' in the description, but its format (Discord user ID) and how to obtain it are not explained. With 0% schema description coverage, the description adds little meaning beyond the parameter name. The AI must infer what a 'userId' is in Discord context.

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 opens or fetches a DM channel with a user and returns the channelId. It uses a specific verb ('open'/'fetch') and identifies the resource ('DM channel with a user'). Among siblings, it is distinct from discord_get_dms (which lists DMs) and discord_create_group_dm (group DMs), so purpose is 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?

The description implies the tool is used when you need a DM channel ID for a user, but it does not explicitly state when to use this over alternatives like discord_get_dms or discord_create_group_dm. No when-not-to-use or prerequisites are provided, so guidance is adequate but minimal.

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