azeth_list_conversations

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

No annotations provided, so description carries full burden. Adds critical behavioral context not in schema: warns that 'First call may be slow due to XMTP initialization' and describes return value structure ('Array of conversations with peer address and creation time'). However, omits other behavioral details like sorting order, pagination limits, or error conditions.

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?

Excellent structure with clear section headers (implied via 'Use this when:', 'Returns:', 'Note:', 'Example:'). Front-loaded with purpose, zero wasted words. Each sentence provides distinct value (purpose, usage criteria, return format, performance warning, usage example).

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?

Compensates well for missing output schema by describing return values (array with peer address and creation time). Includes performance warning about XMTP initialization. Could be improved by defining 'active' conversations or mentioning result ordering, but sufficient for a simple list operation with one optional parameter.

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%, with the 'chain' parameter fully documented including default behavior and accepted values. Description adds no parameter-specific guidance, but with high schema coverage, baseline 3 is appropriate—the schema handles 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?

States specific verb 'List' + resource 'XMTP messaging conversations' + scope 'active'. Clearly distinguishes from sibling messaging tools like azeth_receive_messages (which gets content) and azeth_send_message (which sends), as this returns conversation metadata/addresses rather than message content.

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?

Provides explicit 'Use this when:' section stating two clear scenarios: checking communication history and verifying if a conversation exists with a specific peer. Lacks explicit 'when not to use' or named alternatives (e.g., contrast with receive_messages), but context is clear enough for selection.

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