Mistral OCR

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeatability profile is covered. The description adds nothing beyond that: no supported formats, no input mechanism (file upload, URL, base64), no mention of rate limits or output shape. For an OCR tool that is almost certainly nondeterministically parsed output, this is a real gap.

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 no filler or repetition. It is efficient, though its brevity is part of the tool's overall under-specification rather than a deliberate trimming of surplus detail.

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?

With no output schema, no parameters, and a description that stops at the purpose, an agent cannot tell how the document is supplied (URL? file ID? upload?) or what the extraction returns (plain text, Markdown, layout metadata). For a 0-parameter OCR tool the description should carry this burden and does not.

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 declares zero properties, so there is no parameter semantics for the description to enrich; per the baseline for 0-parameter tools this scores 4. The description neither misleads nor clarifies the (absent) argument surface.

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 names a specific verb ('Extract text') and resource ('documents and images'), and the phrase 'using OCR' distinguishes it from siblings like mistral_transcribe_audio (audio) or mistral_embeddings (vectors). It does not, however, explicitly position itself against the other document-handling siblings such as mistral_get_file or mistral_upload_file.

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 statement of when to use this tool versus alternatives, nor any prerequisites or exclusions. An agent must infer from the name alone that this is the OCR path rather than the file-download or transcription path.

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