Export to PowerPoint

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the write/local nature is already known. The description adds real value by disclosing the slide-mapping and Morph transition behavior and the default output name, but it says nothing about overwrite behavior for an existing target file, permission requirements, or what is returned on success.

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?

A single tight sentence that front-loads the action and format before the behavioral detail and the default. No filler to trim.

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 file-writing tool with no output schema, the description covers what is produced but omits the return value and overwrite semantics an agent needs to call it safely. It is adequate, not complete.

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 50%: `path` is well documented in the schema while `out` is bare. 'Defaults to the project's name with .pptx' partially compensates by implying the output-name parameter's default, but it never distinguishes `out` from `path` or gives format details for `out`, leaving the ambiguity between the two string parameters unresolved.

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?

States a specific verb and resource ('Exports the presentation to .pptx') plus the output structure (one slide per step, Morph transitions), which clearly separates it from export_pdf and save_as. It stops short of naming those siblings explicitly, so the differentiation is implied by the file format rather than stated.

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?

There is no guidance on when to choose this over export_pdf, save_as, or open_in_editor, and no prerequisites or exclusions. The only usage-adjacent information is the filename default, which is about behavior, not tool selection.

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