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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, covering the safety profile. The description adds one useful scope note – that results include pending 'requests', not just established conversations. It does not mention pagination behaviour for the cursor or how many items come back per call, which is unannotated behavior.

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?

A single economical sentence with the resource front-loaded. No filler, no redundancy.

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 simple read-only list with annotations covering safety and a fully described schema, the description is minimally adequate. It leaves the pagination model (cursor/limit) and result shape unstated, though the absence of an output schema means it could reasonably say a bit more.

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%, so 'view', 'limit' and 'cursor' are fully documented in the schema, including the enum semantics for 'view'. The description adds nothing 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?

Specific verb+resource: 'List your direct conversations and requests.' An agent can distinguish this from send_dm/request_dm/respond_dm, which are the action counterparts. It stops short of explicitly naming those siblings as exclusions, but the scope ('your') is clear.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when to prefer this over alternatives like request_dm or respond_dm. The agent must infer that this is the enumeration counterpart to the sibling action tools.

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