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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real operational context beyond that: this is a reporting endpoint, results include total_records, and pagination must reuse the returned next.search_uuid/next.page/next.page_size exactly. It stops short of describing return payload structure or rate limits.

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?

Three compact sentences, front-loaded with purpose then pagination mechanics, then the raw endpoint. The endpoint path is arguably redundant but small; no filler prose.

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 output schema, the description compensates by naming key returned fields (creator, thread, first-response flags) and the pagination contract (total_records, next.*). Coverage is good for a read-only list tool, though the full post payload shape remains unspecified.

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 the baseline is 3, but the description adds meaning by emphasizing that pagination parameters must be passed back verbatim from the prior response and by noting created-time filtering semantics. This is genuinely useful beyond the schema text.

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 (posts/messages/whispers of one conversation), plus the returned fields (creator, thread, first-response flags, total_records). This clearly separates it from textline_get_conversation or textline_list_conversations, which operate on conversations rather than posts.

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?

Frames the tool as a reporting API scoped to a single conversation and gives explicit continuation instructions for paging. It does not, however, state when to prefer this over sibling tools or any prerequisites (e.g. needing a conversation UUID first).

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