create_powerpoint_from_template

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

No annotations are provided, so the description carries the full burden. It discloses that the template's background is inherited and new slides are generated, but omits other important behaviors such as whether existing files are overwritten, how the XML is validated, or what the return value is. For a file-creation tool with no annotations, this is insufficient.

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 a single, front-loaded sentence that immediately communicates the usage context and core behavior. Every clause earns its place with no unnecessary filler.

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?

Despite having 5 parameters, no annotations, and no output schema, the description is only one sentence. It covers the main purpose but lacks details about expected output, error handling, file overwrite behavior, or validation requirements. This is incomplete for a tool of this complexity.

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 coverage is 100%, so the baseline is 3. The description adds a small amount of meaning by explaining that templatePath's background is inherited, but this is already stated in the schema's parameter description. Thus the description contributes no significant semantic value beyond the schema.

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 the tool creates a PowerPoint from an existing template, inheriting the template's background. The verb 'create...from_template' and the specific mention of template usage distinguish it from the sibling create_powerpoint tool.

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 begins with '【テンプレート使用時】' meaning 'when using a template', explicitly indicating when this tool is appropriate. It does not mention exclusions or name the alternative create_powerpoint, but the context is clear enough for an agent to choose between the two.

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