Append to Conversation

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the agent knows this mutates state and is not repeat-safe. The description adds nothing beyond that – no indication of whether appended messages trigger a completion, how ordering/roles are validated, or what the call returns. With annotations carrying the safety profile, the description still fails to add useful behavioral context.

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?

A single front-loaded sentence with zero waste. It is efficient, though its brevity is part of why other dimensions are thin rather than a strength in itself.

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 two-parameter append tool with no output schema and full schema coverage, the minimum viable information is present. However, the nested message structure invites questions (role ordering, system/user sequencing, whether appending triggers inference) that the description leaves entirely unanswered.

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% and the nested message schema (role enum, content variants, tool_calls) is richly typed, so the schema does the heavy lifting. The description adds no parameter detail, which is the expected baseline 3 when coverage is complete.

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 specific verb ('append'/'Add messages') and resource ('an existing conversation'), which clearly separates it from mistral_create_conversation and mistral_get_conversation_history. It stops short of naming a sibling, so it does not reach the top of the scale.

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 'existing conversation' implies the conversation must already exist, but there is no explicit when-to-use guidance and no mention of alternatives such as mistral_create_conversation (for new threads) or mistral_agents_completion. Nothing tells the agent when this is the right call versus other conversation tools.

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