list_conversations

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

With no annotations provided, the description carries the burden of behavioral disclosure. It conveys that the operation is read-only ('List') and authentication-dependent ('authenticated inbox'), and hints at recency. Still, it does not specify ordering, whether results are paginated, or what happens when the user is not authenticated.

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 two concise sentences with the core action front-loaded and the parameter explanation kept in a clear 'Args:' block. There is no redundant or filler content.

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?

For a simple tool with only one optional parameter and an output schema available, the description is largely complete. It could be improved by noting ordering/pagination or pointing to get_conversation_messages for reading a specific conversation's messages, but these are minor gaps for this use case.

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 0%, but the description fully compensates for the sole parameter 'limit' by defining it as 'Maximum conversations to retrieve' and stating the default and max values. This adds meaningful usage semantics beyond the bare schema definition.

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 recent direct message conversations from your authenticated inbox.' This clearly identifies what the tool does and differentiates it from sibling tools like get_conversation_messages, which handles individual messages rather than conversation listings.

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 'from your authenticated inbox' implies the tool is for retrieving the user's own recent DMs, giving some usage context. However, it does not explicitly state when to use this tool versus alternatives such as get_conversation_messages or get_feed, nor does it mention any exclusions.

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