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

Goes well past the readOnly/idempotent annotations: it declares the output is text-only with no external files or scripts, and explicitly lists what is NOT carried over (charts, SmartArt, video, audio, animations, surfaced via notCarried). That loss disclosure is exactly the kind of behavioral fact an agent cannot infer from annotations or schema.

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?

One dense paragraph that front-loads the conversion and then layers exclusions and flag defaults; almost every clause carries information. The only wasted token is the odd 'from freedailypro' qualifier, which adds no actionable 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?

With all five parameters documented in the schema and no output schema, the description supplies the missing return-shape and fidelity information (text output, inlined images, omitted media types) plus flag defaults. An agent can call this correctly and set expectations about the result without further probing.

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 100%, so the baseline is 3. The description reinforces the defaults for includeNotes and includeHidden, but says nothing about the `look` enum (deck/light/dark) or `title`, leaving those entirely to the schema.

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 a precise resource transformation: convert a .pptx into ONE self-contained HTML file returned as text. It also enumerates the resulting artifact (inlined images, arrow-key nav, G grid, N notes), so the agent knows exactly what it gets and can distinguish it from the many pptx_* siblings that mutate decks or the *_to_pptx tools that go the other direction.

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 named alternative, but none exists among the siblings, so the routing is unambiguous. It does give operational guidance on the two optional flags' default behavior (notes off unless includeNotes, hidden slides omitted unless includeHidden), though it never says when to prefer this over, say, pptx_extract_text for a plain text dump.

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