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

With no annotations at all, the description carries the full behavioral burden and leaves the important traits unstated. It never says how many conversations come back, how "recent" is bounded, what ordering applies, or whether auth/session is required. For a listing tool with zero annotation coverage this is a meaningful gap, though the read-only nature is strongly implied by "List".

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 front-loaded sentence with no filler or redundancy. Every clause earns its place by naming the resource, the scope, and the surface.

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 one-parameter read tool with no output schema, the description is minimally adequate but does not tell the agent what a returned "conversation" contains (participants, last message, unread state) or how many are returned. Without an output schema, that return-shape ambiguity is left entirely unaddressed.

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% and the single parameter (notification_message) is fully self-documented in the schema, so the baseline of 3 applies. The description adds nothing about that parameter, but it also does not need to.

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 pairs a specific verb ("List") with a well-defined resource ("private message conversations") and scopes it to the in-game Phone app, which cleanly separates it from send_dm and get_chat_with_player. It stops short of naming a sibling explicitly, so an agent must infer the inbox-vs-conversation distinction.

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: the word "recent" suggests an inbox/overview call, and the Phone app framing hints at the in-game messaging surface. There is no statement of when to prefer this over get_chat_with_player or list_contacts, and no prerequisites or exclusions are mentioned.

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