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

With no annotations, the description carries the burden and does substantially more than most: it defines the exact inclusion rule ('they messaged last, not yet actioned') and gives a careful caveat on hiring_signal — badge-only, cached from a prior fetch, never a live fetch, and false means 'nothing to report' rather than a confirmed negative. That prevents a real misread. It still omits ordering, result volume, and whether results are truncated, 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?

The filter definition is front-loaded in the first sentence and the follow-up tool routing comes second, so the agent gets the gist immediately. The hiring_signal paragraph is long but earns its length by preventing a misinterpretation. The trailing '### Responses: **200**: Successful Response' block is auto-generated boilerplate that adds nothing.

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 input params and no output schema, the description must cover what comes back, and it does at a high level ('chat handles'). The hiring_signal field is explained in depth. What is missing for a listing tool is ordering, page size, and truncation behavior — an agent cannot tell how many threads to expect or whether it needs to paginate.

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?

Zero parameters, so there is nothing for the description to document and the baseline is 4. The hiring_signal explanation usefully characterizes a returned field rather than an input, which is bonus context rather than compensation.

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 a specific verb ('List') and a precisely scoped resource: inbound threads where the counterparty messaged last and no action has been taken. That scoping parenthetical is what separates it from list_chats / list_reply_drafts without naming them, so an agent can reason about the difference. It stops short of explicitly contrasting with the sibling listing tools, which keeps it at 4 rather than 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?

It implies the downstream workflow well ('Returns chat handles ready for draft_reply / get_thread / schedule_chat_reply'), so the agent knows what to do next with results. However, it never says when NOT to use this tool or names the alternative (e.g. list_chats for the full inbox, find_stale_threads for aging threads). Usage is inferable but not differentiated.

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