Repair a .pptx against the OOXML spec

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

The description discloses specific mutations: backfilling ID-list entries, correcting content types, removing dangling relationships, stripping printer-settings parts, and clamping geometry. It also states it returns a change log and reports unfixable violations instead of guessing, which adds meaningful behavioral context beyond the readOnlyHint=false and idempotentHint=true annotations.

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 dense but purposeful: it front-loads the core action, then uses a colon to introduce a specific list of fixes, and closes with the output/log behavior. Every clause adds useful information, with no filler or tautological repetition of the title.

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?

For a single-parameter repair tool with a true output schema and annotations covering read-only/idempotence, the description supplies all essential context: what will be fixed, what will be removed, and how unsafe violations are handled. Nothing critical appears missing for an agent to decide whether and how to invoke it.

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?

The description adds only that the tool operates on an existing .pptx and returns a repaired file; it does not explain how to provide the source via path versus base64. However, the input schema itself documents the nested path and base64 properties well, so the parameter semantics are still usable without requiring the description to compensate.

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 uses a specific verb and resource: "Auto-fix an existing .pptx's structural problems," then enumerates concrete repair actions. This clearly distinguishes it from sibling tools like pptx_validate and pptx_audit, which are inspection-oriented rather than repair-oriented.

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 intended use is implied by "auto-fix" and the enumerated structural defects, so an agent can infer this is for repairing broken OOXML packages rather than creating or auditing them. However, the description never explicitly names alternatives such as pptx_validate or pptx_audit, nor does it state when not to use this tool.

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