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

Beyond the annotations, the description explains that the tool returns a new editable base64 .pptx, preserves the slide master, layouts, theme, notes, pictures, charts, and tables, and errors when a slide number does not exist or every slide would be removed. This is substantial behavioral context, and it is consistent with readOnlyHint because the original file is transformed rather than mutated in place.

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 front-loaded with the main action and output, then maps each parameter clearly. Despite being dense, every clause carries useful information about output preservation, ordering, or error behavior.

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 five-parameter mutation-style transformation with annotations but no output schema, the description covers what the tool returns, what is preserved, key parameter behavior, and error conditions. It could go further by describing the response envelope or edge-case interactions between order, remove, and duplicate.

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%, so the baseline is 3, but the description adds important semantics: order is a final 1-based ordering where repeating a number creates a copy, remove and duplicate target original slide numbers, removeHidden deletes hidden slides, and all numbers refer to the ORIGINAL deck. It does not fully clarify interactions among order, remove, and duplicate, so it falls short of a 5.

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 specific verbs and resource (reorder, delete, duplicate slides of a .pptx) and states the output is a new editable .pptx. It is clearly distinguishable from sibling tools such as pptx_merge, pptx_split, and pdf_organize.

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 clearly establishes the use cases for organizing slides and explains the core parameters, so an agent can tell when to call it. However, it does not explicitly name alternatives such as pptx_split or pptx_merge, nor does it state when not to use it.

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