powerpoint_create_from_template

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

Annotations already declare this as a non-read-only, destructive, non-idempotent write. The description adds non-obvious behavior beyond that: native PowerPoint execution with hidden presentation windows and that the source template is left unchanged. It omits overwrite behavior on outputPath and any failure-mode or idempotency context.

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?

Two tight sentences with purpose front-loaded and no filler. Each clause contributes either scoping information or behavioral context.

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 five-parameter creation tool with a complex oneOf slides schema, no output schema, and only 40% parameter description coverage, the description covers core mechanics and template safety. It still omits sibling-routing guidance and the overwrite/keepTemplateSlides behavior an agent needs before invoking it.

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 40%, so the description needs to compensate more than it does. It conceptually maps to the two slide source modes and to filling placeholders or named text shapes, but never mentions templatePath, outputPath, overwrite, or keepTemplateSlides, leaving those semantics to the schema alone.

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), resource (PPTX), and source modes (existing deck's masters/layouts or duplicated slides) plus the filling operations. It implicitly distinguishes itself from from-scratch creation tools, but does not name an alternative or explicitly say when to prefer it over siblings like powerpoint_create_presentation or powerpoint_create_designed_presentation.

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 implies the applicable scenario: template-based creation by filling placeholders or named text shapes. However, it gives no when-not guidance, no prerequisites, and no explicit routing among the several sibling presentation-creation tools.

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