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

Goes well beyond the readOnly/destructive/openWorld annotations by disclosing that all reads share one browser session, that results carry weOweReply, that the reply includes oweReply/noThread/failedReads counters, and the exact distinction between `failed` (read did not work) and `noThread` (no conversation exists). That error-semantics detail is genuinely useful and not derivable from structured fields.

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?

Front-loads the core action and scope, then routes to alternatives, then covers result/error semantics in a tight sequence with no filler. Dense but every sentence earns its place; the only minor cost is the cluster of backticked result-field names that reads slightly heavily.

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 4-parameter read tool with no output schema, the description supplies what is otherwise missing: return-field meaning (weOweReply and the counters), per-person failure semantics, single-session behavior, and account defaults are covered by the schema. An agent has everything needed to call and interpret it.

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 profileUrls, perThreadLimit, sessionId and sessionLabel. The description echoes the 'last N messages' and 'up to 100' limits but adds no syntax or format detail beyond what the schema provides, so the 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?

States a specific verb and resource (read the last N messages of threads for many named people, up to 100) in the first sentence, and explicitly contrasts itself with three siblings: li_list_conversations, li_read_conversation, and li_conversation_history. An agent can select it without opening any schema.

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?

Gives an explicit selection condition ('use it when you know WHO') and then names each alternative with the behavior that distinguishes it (inbox by recency, one-person form, already-stored threads). It also states a preference rule: one big call over several small ones.

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