pptx-to-markdown

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 omits critical details such as error handling for invalid files, output format specifics, performance expectations, or any side effects. This is inadequate for a tool with no annotation support.

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—it directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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, lack of annotations, and no output schema, the description is incomplete. It fails to address output format, error cases, or behavioral traits, leaving significant gaps for an agent to operate effectively. This is particularly problematic in a server with multiple similar tools.

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 adds no additional parameter semantics beyond implying the input must be a PPTX file, which is redundant with the tool name. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 the resource 'PPTX file to markdown', making the purpose immediately understandable. It distinguishes from siblings by specifying PPTX format, though it doesn't explicitly contrast with other conversion tools like 'docx-to-markdown' or 'pdf-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?

No guidance is provided on when to use this tool versus alternatives. With multiple sibling conversion tools (e.g., docx-to-markdown, pdf-to-markdown), the description lacks context on file format suitability, prerequisites, or comparisons, leaving the agent to infer usage based on file extension alone.

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