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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond the structured fields: results are grouped one-per-contact and each carries contact and resolved status, and it identifies the underlying GET endpoint.

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 clauses with the core scope ('list conversations one per contact in a department') front-loaded, followed by the optional-search note and endpoint. No wasted wording.

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?

All four parameters are schema-documented, annotations fully cover the read-only/idempotent profile, and no output schema exists so return values need not be explained. The description is sufficient to call the tool correctly, with only sibling routing left implicit.

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 all four parameters (page, query, page_size, group_uuid) are already documented in the schema. The description only echoes the optional keyword search and adds no format or syntax detail beyond that, which is the baseline when the schema does the heavy lifting.

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 gives a specific verb (List) and resource (conversations), plus the useful granularity 'one per contact' and the department scoping. It implicitly distinguishes itself from the singular textline_get_conversation, but does not name that or any other sibling explicitly.

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 phrase 'Optional keyword search' hints at when the query parameter is relevant, but there is no explicit when-to-use vs. alternative guidance. An agent must infer that this is the broad listing tool rather than textline_report_conversations or the single-conversation getter.

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