powerpoint_render_presentation

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so safety is covered. The description adds one genuinely useful trait the annotations cannot convey: rendering goes through 'real Microsoft PowerPoint,' implying an installed-Office dependency and faithful native rendering. It does not explain what gets written/overwritten on disk despite destructiveHint=true, so credit is partial.

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?

A single front-loaded sentence with no filler: verb, engine, output format, and intended workflow. Every clause earns its place.

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?

The output form is stated and there is no output schema to compensate for, but the 33% schema coverage and the silent maxSlides=10 default (which silently truncates renderings) mean an agent could call this and misread the result. The write/overwrite behavior also goes unaddressed.

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 33% — width, height, maxSlides, and overwrite have no description text. The description mentions none of them, leaving the default maxSlides=10 cap and the overwrite flag completely unexplained by either source.

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 (Render), a specific resource (PPTX with real Microsoft PowerPoint), and the distinct output artifact (slide PNGs as MCP images). The phrase 'real Microsoft PowerPoint' differentiates it from a structural sibling like powerpoint_inspect_presentation, so an agent can route correctly without opening a schema.

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?

'for visual inspection and iterative correction' gives a clear scenario context for when to reach for this tool. There is no explicit when-not or named alternative (e.g., use inspect for structural checks instead), so it stops short of full routing guidance.

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