list_conversations

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

No annotations provided; description discloses return fields and name resolution from local contacts. Does not explicitly state read-only nature but it is implied. Adequate but could mention side effects (none) or auth requirements.

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?

Concise with multiple sentences each adding value. Front-loaded with purpose, then return fields, usage guidance, and alternatives. No unnecessary words.

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 no output schema, description explains all return fields adequately. Covers ordering, returned data, name resolution. Complete for a simple list 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?

Input schema has zero parameters, so baseline is 4. Description does not add param info because none exist. Appropriate.

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?

Clearly states it lists all conversations ordered by most recent message and specifies the returned fields. Explicitly differentiates from sibling tools like get_conversation and get_unread.

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 usage context: use for inbox overview before reading specific conversations, and warns not to use for reading message history. Names alternative tools get_unread and get_conversation.

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