Get Conversation History

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. The description adds no behavioral context beyond what annotations provide — it does not explain what 'full' includes (e.g., pagination, ordering, message format) or any rate limits. No contradiction with annotations is present.

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 efficient sentence with no wasted words and the key action is front-loaded. However, it is arguably too sparse given the tool's role among siblings, but the structure itself is clean and not verbose.

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 simple lookup tool with full schema coverage and safety annotations, the description is minimally adequate. It does not clarify the distinction from mistral_get_conversation, which could confuse an agent selecting between the two. No output schema exists, so the description needn't explain return values, but the lack of differentiation is a 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% and the single parameter conversation_id is documented in the schema. The description does not add any meaning beyond what the schema provides. Baseline 3 is appropriate when the schema fully covers parameter semantics.

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 specific verb and resource: 'Get full conversation history.' It is clear what the tool does, but it does not differentiate itself from sibling tools like mistral_get_conversation or mistral_list_conversations. No indication is given of how 'full history' differs from other retrieval tools.

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 guidance on when to use this tool versus alternatives such as mistral_get_conversation or mistral_list_conversations. No conditions, prerequisites, or exclusions are mentioned. The description simply states the action without context for selection.

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