powerpoint_create_designed_presentation

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and non-idempotent, so the safety profile is partly covered. The description usefully adds format traits (widescreen, typography, imagery) and a post-create verification workflow, but it never discloses the destructive/overwrite behavior implied by destructiveHint=true and the 'overwrite' parameter defaulting to false.

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 front-loaded sentences with no filler, and the use-case preference plus verification step are compactly stated. The first sentence leans on undefined adjectives ('editorial compositions,' 'readable typography') that spend words without adding precise meaning.

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 complex creation tool with 5 parameters, a nested oneOf slide union, no output schema, and a destructive overwrite flag, two sentences are insufficient. An agent cannot learn the layout vocabulary, style effects, or overwrite semantics from the description, and no structured field fills those gaps.

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 only 20%, so the description must compensate and does not. It gestures at style ('editorial compositions') but never explains the editorial/cinematic enum, the five slide layout variants (cover, imageText, statement, comparison, panorama), the overwrite flag, or path semantics, leaving most parameters undocumented in both places.

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 widescreen narrative deck') with concrete attributes (editorial compositions, readable typography, optional cropped imagery). It hints at differentiation from other create tools via 'Prefer this for new story decks,' but never names the sibling it is preferred over (e.g. powerpoint_create_presentation or powerpoint_create_from_template), so the boundary is inferred rather than stated.

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?

Gives clear use context ('new story decks') and a workflow directive ('render and critique the result before delivery'). It does not name an alternative tool for non-story decks or state when-not-to-use, so routing requires inference, but the usage signal is stronger than a bare description.

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