create_slide_from_template

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

Annotations provide only a title, no read-only or destructive hints, so the description carries full responsibility for describing side effects. It merely says 'Create' and lists parameters, but does not disclose whether a presentation must already be open, where the slide is inserted, whether existing content is modified, or what side effects occur.

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 efficient: a single one-line summary followed by a compact Args list. Each parameter entry is short and adds meaning beyond the schema, with no fluff or repetition.

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?

The parameter semantics are well covered and an output schema exists, but the description lacks usage context and behavioral transparency. An agent would understand what arguments to pass but not fully understand the operation's side effects or when to choose it over similar sibling tools.

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%, but the description compensates excellently by explaining every parameter with concrete examples: template_id values, color_scheme options, content_mapping roles, image_paths roles, layout_index meaning, and presentation_id fallback behavior.

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 states a specific action and resource: 'Create a new slide using a layout template.' This clearly differentiates from broader tools like add_slide or create_presentation_from_template, though it does not explicitly name sibling tools or draw a contrast with apply_slide_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?

No guidance is given on when to prefer this tool over alternatives such as apply_slide_template, add_slide, or create_presentation_from_template_content. The description indicates what the tool does but not the conditions that make it the right choice.

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