batch_translate_powerpoint

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

There are no annotations, so the description carries the full responsibility for behavioral disclosure. It only states scope and recursion; it does not mention where output files are written, whether source files are modified, cost implications, caching, model defaults, or any dry-run behavior. For a batch mutation-like operation, this is a meaningful transparency 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 a single focused sentence with the core action front-loaded and the recursive option included as a compact parenthetical. There is no fluff, and every component contributes to the primary selection decision.

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?

For a 16-parameter tool with no annotations, this description is quite sparse, but the rich input schema and existence of an output schema reduce the burden. It still omits useful high-level context, such as how the output folder is determined, whether files are overwritten, and how dry-run behaves, but it is sufficient for a straightforward batch translation call.

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 already provides detailed descriptions for 88% of parameters, including defaults, so the description does not need to repeat parameter semantics. The only parameter-related mention is the recursive parenthetical, which adds marginal value over the schema's own recursive parameter description, so the baseline 3 is appropriate.

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 names a specific verb and resource ('Translate all PowerPoint files in a folder') and adds a recursive scope trait. It clearly distinguishes this from siblings such as translate_powerpoint, translate_specific_slides, or batch_export_powerpoint_markdown, even without naming them.

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 gives a clear usage context: use this when you want to translate every PowerPoint file in a folder, optionally recursing into subfolders. It does not explicitly name sibling tools for single-file translation or exclusion rules, but the folder-scoped phrasing makes the intended invocation obvious.

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