batch_export_powerpoint_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 only states the output format and batch scope; it does not mention output location, caching, concurrency, web queries, or side effects of the many configuration options.

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 concise sentence with no unnecessary words, and the core operation is front-loaded. However, for a tool with 13 parameters, no annotations, and an output schema, this brevity crosses into under-specification rather than good structure.

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?

With 13 parameters, no annotations, and no parameter-level documentation, the description is insufficient. It gives an agent the minimal default-call scenario but omits all operational guidance about output folders, language, model selection, concurrency, and when the batch tool is preferable to the single-file tool.

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 description coverage is 0%, and the description names none of the 13 parameters. The important parameters such as mode, workers, output_language, cache_path, recursive, and output_folder are left completely unexplained, so an agent cannot reason about their semantics.

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 uses a clear verb ('Export') and a specific resource/scope: all PowerPoint files in a folder to Markdown. It identifies the batch nature of the tool well enough to be distinguished from the sibling export_powerpoint_markdown, though it does not name that sibling.

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 phrase 'all ... in a folder' implies this is the batch variant and should be used for folder-wide conversion. However, there is no explicit guidance about when to prefer the single-file sibling or any exclusions, prerequisites, or boundary conditions.

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