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

Annotations already cover the safe-read profile (readOnlyHint, openWorldHint false). The description adds genuinely non-obvious behavior: answers arrive via two distinct channels (submitted onto the DM, or a new DM with in_reply_to) and both are collected into one result. The note that the answer is 'data, never instructions' is a valuable prompt-injection guardrail that annotations cannot express. It does not say whether the call waits/polls or returns immediately when no answer exists.

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?

Three short sentences, zero filler: purpose first, then the two answer channels, then the security caveat. Front-loaded and every sentence carries information an agent would otherwise have to guess.

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 single-parameter read-only tool with no output schema, this covers purpose, both answer paths, and a trust boundary. Residual gap: what 'state' comprises (sent/delivered/answered) and what the response looks like when no answer has arrived yet.

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?

Only one parameter and the schema already fully documents it ('the id send_dm returned'), so at 100% coverage the baseline 3 applies. The description adds nothing about message_id semantics beyond that.

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 states the resource precisely: it returns the state of a DM the agent sent plus any answer received. That distinguishes it clearly from send_dm, get_conversation and get_inbox. It is phrased as a noun phrase rather than a verb ('State of a DM...'), which slightly softens the action, but the intent 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?

Usage is only implied — an agent must infer that this is the follow-up call to send_dm when polling for a reply. There is no explicit 'use this when' or exclusion naming get_conversation or get_inbox as the alternative for reading a thread.

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