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

Annotations declare destructiveHint=true and readOnlyHint=false. The description adds useful context beyond them: moveTo shifts other slides, skipped hides without deleting, and notes replaces existing notes. It does not discuss undo or permissions, but it meaningfully clarifies side effects.

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?

Front-loads the overall purpose, then lists supported parameters compactly, and ends with routing guidance. No sentence is wasted.

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?

Covers operation scope and sibling alternatives, and no output schema means return values need not be explained. Missing only minor details such as reversibility or required permissions beyond the schema's workspace note.

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%, and the schema already documents each parameter. The description repeats key semantics (1-based moveTo, skipped hides, notes markdown) and adds only that other slides shift around the moved slide, so the baseline of 3 is appropriate when structured data does most of the work.

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 resource ('Changes one slide as a whole') and enumerates the four supported operations: move, hide, page-number toggle, and speaker-notes replacement. It also explicitly distinguishes this tool from content-editing siblings napkin_slide_fill and napkin_draw.

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?

Names the alternatives for changing slide content ('use napkin_slide_fill or napkin_draw') and points to napkin_deck_outline as the source for slide numbers. This gives clear when-to-use and when-to-use-something-else guidance.

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