list_conversations

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

With no annotations, the description must carry behavioral disclosure. It adds useful behavior: conversations group messages/voice sessions per contact/channel, channel can be omitted, and limit has a default and maximum. However, it does not clarify status lifecycle values, ordering, or explicitly confirm read-only behavior beyond the verb 'list'.

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 compact and well-structured: a one-line summary, a one-sentence definition of a conversation, and a concise Args list. Every sentence earns its place, and the most important information is front-loaded.

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?

Given that an output schema exists, the description does not need to explain return formats. It covers the core listing purpose, channel filtering, and limit behavior. Gaps such as status values and ordering prevent a perfect score, but it is still a solid description for an inbox-style listing tool.

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?

The input schema has 0% description coverage, so the description's Args block is essential. It explains 'channel' with enum values and omit behavior, and 'limit' with default and max. The 'status' parameter is only described as 'Conversation lifecycle filter', which is too vague to help the agent choose valid values.

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 opens with a specific verb and resource: 'List conversation threads across SMS, WhatsApp, and voice.' It clearly defines what a conversation is and explicitly differentiates from sibling tools like list_calls and list_conversation_messages by emphasizing channel-based grouping and inbox-style review.

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 'Use this for inbox-style review' provides clear usage context, and the channel parameter signals the intended filtering use case. It does not explicitly name alternatives or exclusions, but the description's scope makes it clear when this tool is appropriate.

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