mistral_clear_context_bias

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

The annotations already indicate destructiveHint=true and idempotentHint=true, so the description carries a lower burden. It adds 'all' to clarify scope, but does not disclose additional behavioral aspects such as whether the clear affects only the current session or global state, or if it is reversible. It is consistent with annotations, so no contradiction.

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 concise sentence that is front-loaded with the action and object. It is appropriately sized with zero wasted words, making it easy to parse quickly.

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 parameterless tool with an output schema, the description is mostly complete. The only minor gap is that 'context bias terms' could be more explicitly defined, but the sibling tools and schema provide enough context to understand the tool's purpose.

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?

The input schema has zero properties, so the baseline is 4. The description does not need to explain parameters as there are none. It adds meaning by describing the tool's action, which is sufficient for a parameterless tool.

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 'Clear all context bias terms' uses a specific verb (Clear) and clearly identifies the resource (context bias terms). It distinguishes itself from sibling tools like mistral_set_context_bias and mistral_get_context_bias, making the purpose unambiguous.

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 (clearing all context bias terms) but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, preconditions, or when not to use it, so the usage context is only inferred.

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