List DM conversations

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds useful behavioral context by stating it operates on the authenticated account's conversations and by noting that conversation ids are consumed by other DM tools.

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 concise sentences with no filler. The first sentence states the resource and returned fields; the second explains why the tool matters downstream. Every sentence earns its place.

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?

This is a simple read-only listing tool with two well-documented optional parameters, a rich output schema, and annotations covering its safe, open-world behavior. The description fully explains what it returns and how the result should be used, so nothing essential is missing.

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 input schema already documents both parameters with full description coverage (100%). The description adds no parameter-specific meaning, so the baseline score of 3 is appropriate; the schema carries the weight here.

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 identifies a specific verb ('List'), a clear resource ('direct-message conversations'), and lists the returned fields (ids, participants, last message, unread counts). It is easily distinguishable from sibling DM tools because it focuses solely on conversation listing rather than messages, sending, or unread counts.

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 sentence 'The conversation id feeds every other DM tool' gives clear context for when to use this tool: as the entry point before using other DM operations. It does not explicitly name alternatives or state when not to use it, but the downstream role is clearly conveyed.

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