list_conversations

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context by specifying the resource is 'inbox conversations (email replies)', clarifying the scope. It also mentions pagination, which is not in annotations. No contradictions.

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 a single sentence that begins with the verb and resource, immediately stating what the tool does. It includes all key capabilities (filtering and pagination) with no filler. Every word serves a purpose.

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 the presence of an output schema (not shown but noted as true), the description appropriately omits return details. It covers the primary functionality (listing filterable conversations with pagination). However, it doesn't mention that all parameters are optional or default behaviors (like page=1, limit=20), which the schema provides but could be reiterated for clarity.

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 the schema already documents all 6 parameters. The description summarizes filters (status, search, unread) and pagination, adding context that these apply to inbox conversations. This adds value but is not extensive, fitting the baseline of 3.

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 clearly states the action ('List'), the resource ('inbox conversations'), and specifies filtering options ('by status, free-text search, or unread state') and pagination. It distinguishes this tool from siblings like 'get_conversation' (single conversation) and 'reply_to_conversation' (action) by framing it as a list operation for email replies.

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 description implies usage for listing email replies from subscribers, but it does not explicitly state when to use this tool versus alternatives such as 'get_conversation' for a single conversation or 'search_subscribers' for subscriber data. No guidance on when not to use it or prerequisites is provided.

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