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

No annotations are provided, so the description carries the full disclosure burden, yet it only implies a read operation. It says nothing about authentication requirements, result volume, ordering, or whether the list is paginated, all of which matter for a listing tool.

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?

Four words, front-loaded and free of waste, but also so terse that it borders on under-specification rather than disciplined brevity. Structure is fine; substance is thin.

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?

The tool is simple and the single parameter is fully documented, but with no output schema the description should at least sketch what a returned thread looks like or how results are bounded. As written, an agent cannot predict the response shape at all.

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 optional parameter is documented there, so the baseline is 3. The description adds nothing about notification_message, which is a non-obvious fallback-message parameter for a listing operation that could use extra clarification.

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?

States a specific verb (List) and resource (Direct inbox threads), which is enough to tell it apart from write-oriented siblings like send_dm and from single-thread tools like direct_thread. It never explicitly contrasts with direct_pending, however, leaving ambiguity about how 'inbox' relates to 'pending'.

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 statement of when to use this versus direct_pending or direct_thread, no prerequisites, and no indication of ordering, pagination, or result limits. The agent must infer everything about invocation context from the tool name alone.

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