Convert PowerPoint presentations to Markdown format for easier editing, sharing, and documentation purposes.
Convert a PPTX file to markdown
| Name | Required | Description | Default |
|---|---|---|---|
| filepath | Yes | Absolute path of the PPTX 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. It states the conversion action but lacks behavioral details: it doesn't mention if the tool overwrites files, requires specific permissions, handles errors, or outputs to a specific location. For a file conversion tool with zero annotation coverage, this is a significant gap in transparency.
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, efficient sentence with zero waste: 'Convert a PPTX file to markdown'. It is front-loaded and appropriately sized, earning its place by clearly stating the core functionality without unnecessary elaboration.
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 (which involves input/output handling and potential errors), no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., markdown text, file path), error conditions, or dependencies, leaving gaps for an AI agent to use it correctly.
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 well-documented as 'Absolute path of the PPTX file to convert'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.
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 'Convert a PPTX file to markdown' clearly states the verb 'Convert' and the resource 'PPTX file', making the purpose immediately understandable. It distinguishes from siblings by specifying the PPTX format, though it doesn't explicitly differentiate from similar conversion tools like 'docx-to-markdown' beyond the file type.
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 siblings like 'docx-to-markdown' and 'pdf-to-markdown', it doesn't specify scenarios where PPTX conversion is preferred or any prerequisites (e.g., file format compatibility). Usage is implied by the tool name but not articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.