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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description contributes only the pagination behavior, which is thin additional context for a read-only list tool.

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?

Two short sentences, but the first ('Conversations List') merely restates the title and earns no place. The remaining sentence is front-loaded and non-redundant, but the whole is under-specified rather than genuinely concise.

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 an 8-parameter, zero-required list tool in a namespace crowded with conversation-related siblings and no output schema, the description omits what is returned, default filtering behavior (status defaults to 'open'), and how it differs from adjacent tools. Too little to call it correctly with confidence.

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 63%, in the mid band, and the description adds nothing about the parameters — it only restates pagination, which the `page` parameter already documents. Undocumented params like labels, team_id, and inbox_id get no explanatory help from the description.

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 clear verb+resource ('List all the conversations') and adds scope ('with pagination'), so an agent knows it is a paginated list operation. However, it makes no attempt to distinguish itself from siblings like conversation_filter, conversation_list_meta, or list_conversation_messages, which a busy tool namespace needs.

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?

There is no when-to-use guidance at all: no statement of when to prefer this over conversation_filter or the meta/stats variants. The agent must infer selection purely from the name.

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