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

The description thoroughly details behavioral traits such as layout selection, theme fonts, internal unit usage, and font inheritance. It also includes a comprehensive slide mapping section. Annotations are non-contradictory (readOnlyHint=false, destructiveHint=false), and the description adds significant value beyond them.

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 well-organized with clear sections (Features, Slide Mapping, Example) and front-loads the core purpose. The extensive example and feature list are justified by the tool's complexity, though minor condensation could improve conciseness.

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 tool's complexity (5 params, detailed slide mapping), the description provides comprehensive guidance covering input methods, behavior, slide rules, and return value. The absence of an output schema is compensated by clear description of the return structure ('Status dictionary with file path and slide count').

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 100% with descriptions for all 5 parameters. The description adds context beyond the schema by explaining the purpose of markdown_file for large inputs and listing default font values. The detailed slide mapping rules further enrich parameter understanding.

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?

The description explicitly states 'Convert Markdown content to a PowerPoint presentation' and identifies it as 'the primary tool for creating PowerPoint decks.' It contrasts with sibling tools like pptx_add_slide by focusing on full deck creation from text.

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 clearly presents this as the go-to tool for creating decks from markdown. It also provides guidance on using markdown_file for large inputs to avoid size limits. While it does not explicitly list when not to use it among siblings, the context implies its primary role.

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