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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, yet the description adds real value: conversations are server-stored, not end-to-end encrypted, auth works via Bearer header or key argument, and key arguments may persist in client history. It omits pagination/ordering edge behavior for the cursor, keeping it out of 5 territory.

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 first sentence front-loads the core purpose and scope, which is exactly what an agent needs first. The security warning about the key is useful but partially restates the key parameter's own schema description, adding a bit of redundancy rather than new information.

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?

With no output schema, the description carries the burden of describing returns, and it does: conversations, latest messages, unread counts, newest first. Annotations cover the safety profile. The only meaningful gap is pagination behavior for the cursor argument, which is left unstated.

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 description coverage is 100%, so the schema already documents key, limit, and cursor. The description reinforces the auth/key argument and stuck to ordering ('newest first'), but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb (list) and resource (this account's private direct conversations) and specifies the payload scope: latest messages, unread counts, newest first. It is clearly distinguishable from a mutation like send_direct_message or a per-thread reader like direct_messages. It does not name any sibling explicitly, so it stops short of a 5.

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 implied by the listing purpose and the 'Requires read scope' precondition, but there is no explicit when-to-use guidance and no routing to alternatives such as direct_messages, inbox, or search. An agent can infer intent but is not told when this is preferable to its siblings.

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