Convert DOCX files to Markdown format for easier editing and sharing. This tool transforms Word documents into readable Markdown text.
Convert a DOCX file to markdown
| Name | Required | Description | Default |
|---|---|---|---|
| filepath | Yes | Absolute path of the DOCX file to convert |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the conversion action but doesn't describe what happens during conversion (e.g., formatting preservation, error handling, output location, or performance characteristics). For a file conversion tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.
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 extremely concise—a single sentence with no wasted words. It is front-loaded with the core purpose, making it easy to scan and understand immediately. Every word earns its place by directly contributing to the tool's intent.
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?
Given the lack of annotations and output schema, the description is incomplete for a file conversion tool. It doesn't explain what the output is (e.g., markdown text, saved file), where it goes, or any limitations (e.g., file size, supported DOCX features). With siblings offering similar conversions, more context is needed to differentiate and use this tool effectively.
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 schema description coverage is 100%, with the single parameter 'filepath' well-documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as file format requirements or conversion options. With high schema coverage, the baseline score of 3 is appropriate.
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 clearly states the verb ('convert') and resource ('DOCX file to markdown'), making the purpose immediately understandable. It distinguishes from siblings by specifying the DOCX format, though it doesn't explicitly contrast with other conversion tools like pdf-to-markdown or pptx-to-markdown.
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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for converting different formats to markdown (e.g., pdf-to-markdown, pptx-to-markdown), there is no indication of when DOCX conversion is appropriate or what distinguishes it from other conversion methods.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.