Convert images to markdown format with metadata and descriptions for easy integration into documentation and content.
Convert an image to markdown, including metadata and description
| Name | Required | Description | Default |
|---|---|---|---|
| filepath | Yes | Absolute path of the image 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 mentions that the conversion includes 'metadata and description,' which adds some context about output content. However, it fails to disclose critical behavioral traits such as error handling (e.g., for invalid file paths), performance aspects (e.g., processing time or size limits), or output format details. For a tool with no annotations, this is a significant 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?
The description is extremely concise and front-loaded, consisting of a single sentence that directly states the tool's function. There is no wasted language or redundancy, making it efficient and easy to parse. Every word earns its place by conveying essential 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?
Given the complexity of file conversion and the lack of annotations and output schema, the description is incomplete. It does not explain what the markdown output includes beyond 'metadata and description,' such as formatting details or error cases. For a tool that performs a non-trivial operation with no structured output information, more context is needed to guide the agent 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 input schema has 100% description coverage, with the 'filepath' parameter clearly documented as 'Absolute path of the image file to convert.' The description does not add any meaning beyond this, as it does not elaborate on parameter usage or constraints. According to the rules, with high schema coverage (>80%), the baseline score is 3, which is appropriate here.
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 tool's purpose: converting an image to markdown, including metadata and description. It specifies the verb ('convert') and resource ('image'), making it easy to understand. However, it does not explicitly differentiate from sibling tools like 'pdf-to-markdown' or 'webpage-to-markdown', which perform similar conversions on different file types, so it lacks sibling differentiation.
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. It does not mention any context, prerequisites, or exclusions, such as when to choose 'image-to-markdown' over other conversion tools like 'pdf-to-markdown' for different file formats. This leaves the agent without clear usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.