convert_markdown_to_pptx

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

With no annotations, the description must disclose all behavioral traits. It mentions conversion and optional output path but does not indicate side effects (e.g., file overwriting), required permissions, or error handling beyond 'error message'. This is minimal disclosure.

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 short (5 lines), starts with a clear statement, and uses structured args list. It could be more compact (e.g., bullet points) but is free of redundancy.

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 no annotations and low param coverage, the description should cover prerequisites (e.g., pandoc), output behavior, and error conditions. It omits these, leaving gaps for the agent. The existence of an output schema partially compensates, but the description itself is incomplete.

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?

Schema coverage is 0%, so the description must add meaning. It briefly explains each parameter but lacks depth: e.g., 'reference_doc: Optional reference PPTX for styling' does not specify how styling is applied (template vs. style copy). Adds marginal value over the schema titles.

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 'Convert Markdown to PowerPoint presentation', which is a specific verb-resource pair. It distinguishes from sibling tools like convert_markdown_to_docx or convert_document by specifying the output format (PPTX).

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?

No explicit guidance on when to use this tool versus alternatives like convert_markdown_to_docx or check_pandoc. The description implies usage for PPTX conversion but does not mention prerequisites (e.g., pandoc installation) or when not to use.

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