Create PowerPoint Presentation

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

Annotations already declare destructiveHint=true, indicating the tool creates a file. The description adds that it creates a .pptx file with slides, which is consistent. However, it does not disclose whether the tool overwrites an existing file at the given filePath or if there are any error conditions. With annotations present, the description provides some additional context but misses potentially important behavioral details.

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 brief and well-structured: a main sentence, then an Args section, then examples. Every sentence adds value, and the main action is front-loaded. No unnecessary words.

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 tool's moderate complexity (2 parameters, nested slides object, no output schema), the description covers the slide structure adequately and provides usage examples. However, it lacks information on behavior for existing files and return value, which would make it more 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 description coverage is 100%, so the baseline is 3. The description replicates parameter explanations (e.g., 'Path where the presentation will be created') and provides examples, but does not add significant meaning beyond what the schema already offers.

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 'Create a new PowerPoint (.pptx) presentation with slides containing titles, subtitles, and bullet content.' The verb 'Create' and resource 'PowerPoint presentation' are specific. However, it does not explicitly distinguish from the sibling tool 'office_add_powerpoint_slides', which could add slides to an existing presentation; this slightly reduces clarity.

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 provides three 'Use when' examples that all involve creating a presentation, but it does not specify when not to use this tool or mention alternatives like 'office_add_powerpoint_slides' for adding slides to existing files. The guidance is implied from the context but not explicit.

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