Create a PowerPoint deck

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

Goes well beyond the annotations by disclosing hard limits (300 slides), layout rules (text plus visual side by side), RTL handling for Arabic/Hebrew, table overflow onto extra slides, and cross-application compatibility. It does not mention that a file is written to disk and where, though the `output` parameter partly covers that; readOnlyHint=true is slightly at odds with file creation but the tool is non-destructive in spirit.

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 artifact, then a dense but useful inventory of capabilities. The single long sentence is heavy but every clause carries information; only the compatibility sentence ('Opens in PowerPoint, Keynote...') is close to 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 an 8-parameter generator with no output schema, the description never says what the tool returns (a file path? a status object?) or how errors surface. Behavior and content modeling are well covered, but the return contract is left entirely to inference.

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?

With 63% schema coverage, the description adds real meaning: bullets may be nested, chart types are native and editable, table first row is a header, images come from path or base64. It does not touch `theme`, `slideNumbers`, or `returnBase64` semantics, so it adds value without fully compensating for the schema gaps.

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 concrete verb and artifact ('Build a 16:9 PowerPoint (.pptx) deck') and immediately distinguishes itself from the sibling ai_pptx_to_markdown by being the generator rather than the extractor. The enumeration of slide content types (bullets, paragraph, image, table, chart, notes) makes the scope unambiguous.

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 says it works 'from a simple outline', which implies when it fits, but never names a precondition or an alternative (e.g. when to prefer ai_diagram, or converting markdown first). No when-not-to-use guidance is given, leaving the agent to infer routing.

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