create_presentation_from_template

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

Annotations provide no behavioral hints beyond a title, so the description carries the full burden. It usefully discloses that a presentation_id is returned and required for later calls, but it does not address side effects, permissions, or failure behavior.

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 dense sentences with no filler. The action is front-loaded, and the essential follow-up requirement is stated immediately after the purpose.

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 one-parameter tool with an output schema, the core invocation is fairly complete. It omits guidance on how to obtain or validate template_path and does not position this tool against closely related creation/sibling tools, which matters given the large sibling list.

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 0%, and the description only repeats the idea token file' without explaining path format, supported file types, or where the template_path should come from. For a single self-named parameter this is a small-but-real gap.

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+resource ('Create a new PowerPoint presentation') and identifies the source as a template file. The return of a presentation_id also clarifies what the tool produces, separating it from read/get-style sibling tools.

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 entry-point nature is implied by 'must be passed to all subsequent tool calls,' and the purpose implies when to use it. However, it gives no explicit guidance about choosing between this and similar siblings such as create_presentation_from_templates or create_slide_from_template.

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