create_presentation_from_template

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

No annotations are present, and the description does not disclose behavioral traits such as whether creation is idempotent, what happens on overwrite, or required permissions. The brief description adds minimal transparency.

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 extremely short but lacks essential information, making it under-specified rather than concise. Every sentence should add value; here the single sentence is ambiguous.

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?

Given the presence of an output schema (unknown content), the description still leaves major gaps: 'bound target file' is undefined, no mention of how the template is specified, and no explanation of the overwrite parameter. Incomplete for effective tool selection and invocation.

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?

The only parameter 'overwrite' has a schema with default and title but no description. The tool description does not mention this parameter or explain its behavior, leaving the agent to guess. With 0% schema description coverage, the description fails to compensate.

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?

Description mentions creating a file from PPTX_TEMPLATE but uses vague phrase 'bound target file' without specifying that the tool creates a presentation from a template. The purpose is somewhat clear but lacks specificity and does not distinguish from sibling tools like 'add_slide' or 'presentation_info'.

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 on when to use this tool versus alternatives such as manually creating slides or using other presentation-related tools. No context is provided about prerequisites or typical use cases.

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