List Conversations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that: it does not disclose that results are paginated, what the default page size is, or what a conversation record contains, and 'all' arguably contradicts the paginated behavior.

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?

It is a single short sentence with no padding, so it is never verbose. The brevity is under-specification rather than disciplined conciseness, but there is no wasted structure.

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?

This is a simple zero-required-parameter read tool with full annotation coverage and a fully documented schema, so little is strictly required. Still, with no output schema there is no indication of what a conversation listing returns or how paging metadata is presented, which is the main remaining gap.

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% for the two integer paging parameters, so the baseline is 3. The description neither explains paging semantics nor adds anything beyond the schema, and 'List all conversations' implies an unpaginated result set even though page_size is capped at 100, making it mildly misleading rather than additive.

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 a clear verb+resource ('List' + 'conversations'), so the basic operation is unambiguous. However it gives no differentiation from siblings such as mistral_get_conversation, mistral_get_conversation_history, or mistral_delete_conversation, and 'all' is slightly misleading against a paginated schema.

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, no mention of when to prefer mistral_get_conversation over this listing, and no note on paging through results. The agent must infer all routing decisions from the name alone.

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