Audit a .pptx (validation + quality metrics)

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful context about the report's scope, including portability risk behavior ('strict readers reject bugs that lenient ones silently self-heal'), which goes beyond the annotations. No contradiction with annotations is present.

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 a single, information-rich sentence that front-loads the purpose ('Full report') and then lists concrete report components in a dash-separated series. Every phrase adds value and no filler exists. The structure makes it easy to scan even though the sentence is long.

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 description covers the tool's substantive functionality thoroughly, and an output schema exists so return values need not be described in prose. It is complete enough for an agent to understand the audit scope and expected metrics. The only notable gap is the lack of explicit routing away from pptx_validate, but the 'plus advisory metrics' phrasing largely covers that.

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 0% according to context signals, so the description must compensate by explaining the `source` parameter and the path/base64 tradeoff. It does not: the entire description focuses on the output report and never mentions how to specify the input file. The schema provides some names and types, but the description adds no parameter guidance, leaving a gap for low coverage.

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 states a specific verb and resource: it produces a full audit report of an existing .pptx. It enumerates concrete content ('all structural validation violations, plus advisory metrics') and explicitly includes validation plus quality metrics, which distinguishes it from the sibling pptx_validate. The title reinforces the same distinction.

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 implies when to use the tool: whenever a comprehensive report with validation and metrics is needed. However, it never explicitly states when not to use it, e.g., 'if you only need validation, use pptx_validate', or mentions any alternatives. The usage context is clear but left to inference.

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