powerpoint_create_presentation

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it never mentions the destructive overwrite behavior, that an existing file at 'path' may be replaced, or that creation is non-idempotent.

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 front-loaded sentence with zero filler; the resource type and capability list arrive immediately. It is efficient, though the element enumeration is somewhat schema-redundant rather than informative.

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 9-parameter, deeply nested, non-idempotent, destructive-write tool with no output schema and near-zero schema coverage, one sentence is far too thin. Nothing explains coordinates units, slide sizing, theme application, or the overwrite flag's consequences.

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 only 11% across 9 parameters, so the description is expected to compensate, but it only lists element categories that are already visible in the schema's oneOf branches. Key parameters (theme, layout, overwrite, title/author/company/subject metadata) receive no explanation in either place.

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 (create) and resource (PPTX presentation) and enumerates the supported element types, which lets an agent match it to visual-content generation. It does not, however, differentiate itself from close siblings like powerpoint_create_designed_presentation or powerpoint_create_from_template.

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 tool over the template- or design-based creation siblings, nor any stated prerequisites (e.g. target directory existence, overwrite behavior). The agent must infer selection entirely from the name.

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