Conversations: Conversations List

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

Annotations already declare this as a safe, idempotent read operation, and the description adds useful context: the required User API key header and handling of Persian/Arabic-Indic text and digits. It does not describe return format or pagination limits, but it adds meaningful operational detail beyond annotations.

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 description is short and front-loads the purpose, with endpoint, auth, and localization notes following logically. The '[Conversations]' tag is slightly redundant but does not bloat the text.

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?

The definition is adequate given annotations and full schema coverage, but for an eight-parameter paginated list tool with no output schema, it lacks details about response shape and pagination behavior. The auth and localization notes help, but do not fully close the gap.

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 eight parameters are already documented in the schema. The description only broadly mentions filters and pagination and does not add parameter-specific meaning beyond that baseline.

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 and resource: list conversations with filters and pagination. It is clear what the tool does, but it does not distinguish itself from the sibling gapify_filter_conversations or other conversation-list tools.

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?

Usage is implied by 'list conversations with filters and pagination,' but there is no explicit guidance on when to use this versus gapify_filter_conversations, gapify_list_contact_conversations, or gapify_client_list_conversations.

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