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

Annotations already establish readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the result set carries total_records, and continuation requires replaying the full next.* triple with filters preserved. It does not mention rate limits or auth requirements, so it stops short of a 5.

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 sentences, zero filler: purpose first, then the pagination contract, then the drill-down tool, closing with the endpoint. Every sentence supplies distinct information and nothing is repeated from the schema or annotations.

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 13 parameters, no required fields and no output schema, the description does the needed work by naming total_records and the next.* return shape, which is the main thing an agent must know to paginate. It could say a bit more about the absence of required params (group_uuid vs search_uuid dependency), which is only implied.

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 real semantics the schema only hints at: that next.search_uuid, next.page and next.page_size must be supplied together and that existing filters are retained implicitly. The group_uuid-as-department mapping is also restated usefully in prose.

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 ('list a department's conversations') plus the filter dimensions (created/updated time, resolved, archived, blocked) and the reporting framing. It is clear, but it never distinguishes itself from the sibling textline_list_conversations, leaving the agent to infer why a reporting variant exists.

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 follow-up action ('then use textline_report_posts per conversation') and precise pagination instructions (pass back next.search_uuid, next.page, next.page_size exactly, filters retained). What is missing is when to choose this tool over textline_list_conversations, so no full when/when-not/alternative coverage.

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