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

Annotations already declare this a safe, idempotent, closed read, so the bar is lower. The description adds genuinely useful return-shape detail (newest-first ordering, last message preview, unread indicator), but says nothing about pagination, result limits, or volume, which matters 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?

Two short sentences, zero filler, with the core return content stated before the optional filters. Only the slightly vague opener 'The person's' costs it a point.

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 listing tool with full schema coverage, the description covers purpose and return content adequately. It omits pagination/limit behavior and any indication of total result size, which an agent needs to know before paging through messages.

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 all three parameters are already documented with constraints. The description largely restates them ('with_member_id', 'one programme') while adding only a small clarification that with_member_id matches a member or group; 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?

The description names the resource (message threads), the ordering (newest first), and the payload (last message plus unread flag). It is clear what the tool returns, but "The person's" is ambiguous about whose threads, and it never explicitly contrasts with read_conversation.

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?

The second sentence implies usage through the optional filters ('only the threads with one member or in one programme'), which hints at narrowing a listing. There is no statement of when to prefer this over read_conversation or when to skip it, so guidance is implied rather than explicit.

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