powerpoint_audit_presentation

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing that results are heuristic and may miss issues that require visual inspection — an honesty caveat that shapes how an agent should trust the output.

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 sentences, no filler. The scope enumeration is front-loaded and the heuristic caveat is placed where it matters, after the capability statement.

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?

No output schema exists, so the description reasonably stands in by naming the flag categories an agent can expect. For a 3-parameter read-only audit, the main remaining gap is the meaning of the two numeric threshold parameters.

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% — minimumFontPoints and denseSlideCharacters have bounds and defaults but no prose descriptions. The description's 'small explicit text' and 'dense slides' phrases loosely map to those two parameters, giving partial semantic anchoring, but units and how thresholds are applied remain undocumented.

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?

Specific verb ('audit') + resource ('PPTX') with an enumerated detection scope: off-slide objects, small explicit text, dense slides, missing alt text. It is clearly distinguishable in spirit from powerpoint_inspect_presentation, though it never names a sibling to sharpen the boundary.

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?

It implies the use case (pre-review of a deck) and gives one caution ('render and visually inspect the deck as well'), which points at a complementary tool without naming powerpoint_render_presentation. No explicit when-not conditions or prerequisite/auth guidance.

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