create_presentation

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

With no annotations, the description carries the full burden. It does disclose useful behavior: the path is where the deck will be saved 'later' (so nothing is written on create) and the default is a blank 16:9 deck. It says nothing about overwrite behavior if a file already exists at path, permission or template-validation failures, or what happens to a previously current presentation.

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?

Front-loaded with the action and the state change, followed by a compact Args block. Every sentence carries information; no 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?

For a create tool with zero annotations and no output schema, the essentials (what is created, its default form, and both optional inputs) are covered. Missing state-transition details — what happens to the prior current presentation and the returned identity of the new one — leave a real gap for a plugin-style tool where subsequent calls depend on the current deck.

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%, so the description must supply all meaning, and it does explain both parameters reasonably: path as the eventual save location and template_path as a .pptx/.potx base. It still omits constraints an agent needs, such as whether the path's directory must exist or whether an existing file is overwritten.

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 and resource ('Create a new PowerPoint presentation') plus a meaningful side effect ('make it the current one'). It implicitly distinguishes itself from open_presentation by being about new decks, but never names the sibling, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as open_presentation for existing files. The 'current one' phrasing hints this tool changes session state, but the agent is left to infer that starting a new deck is the selection criterion.

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