check_document_in_local_cacheChecks whether a Docling document is already converted and stored in the local cache, so you can avoid unnecessary reconversion.
Check whether a Docling document is already converted and present in the local cache.
| Name | Required | Description | Default |
|---|---|---|---|
| document_key | Yes | The unique identifier of the document in the local cache. |
| Name | Required | Description | Default |
|---|---|---|---|
| in_cache | Yes |
Changes observed during successful MCP inspections.
v3.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered without help from the prose. The description is consistent with them and adds a small amount of context (it inspects conversion/cache state, it does not mutate), but says nothing about cost, cache scope, or behavior on a miss, which would be the value-add here.
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; every clause (Docling, already converted, local cache) carries information.
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 an output schema present, the description need not explain return values, and one required parameter plus read-only annotations leave little else to cover. A brief note on how this relates to the conversion tool would close the 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?
Only one parameter and the schema documents it fully ('The unique identifier of the document in the local cache'). The description adds no meaning beyond that, so the baseline 3 for high schema coverage applies.
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?
Specific verb ('check') plus resource ('Docling document in the local cache'), with the clarifying detail that 'converted' means already present. It is distinguishable from convert_document_into_docling_document and list_cached_documents, but the description never names those siblings, so the differentiation is inferred rather than stated.
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 'already converted' hints at a pre-conversion probe workflow, but there is no explicit statement of when to call this versus convert_document_into_docling_document or list_cached_documents, and no mention of what to do on a miss.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.