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

Annotations declare readOnly/destructive hints, so the safety profile is covered. The description adds real context beyond annotations: the output is a rendered image matching present mode, it echoes slideIndex/slideCount enabling stepwise navigation, and it warns the text outline can't carry visual content. It doesn't mention pagination, rate limits, or auth nuance (beyond workspace, which the schema covers).

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, front-loaded with what it produces, then navigation and rationale. Efficient and no filler, though the parenthetical about slideIndex/slideCount packs in navigation detail that could be tighter.

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 read-only 3-param renderer with no output schema, the description covers what the tool returns (an image, present-mode-equivalent), how to navigate a deck, and when to use it versus the outline. Nothing an agent needs to call it correctly is missing.

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 boardId, slide, and workspace are fully documented in the schema. The description reinforces the 1-based presentation-order semantics of 'slide' and explains that the result echoes slideIndex/slideCount, but adds no syntax or format beyond the schema. Baseline 3 is appropriate.

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 (renders) plus resource (a single slide of a Napkin deck) plus the equivalence 'exactly what present mode shows, cropped to the slide'. This distinguishes it cleanly from siblings like napkin_deck_outline (text map) and napkin_deck_export.

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?

Explicit when: check visual layout, drawings, and images the text outline can't carry. Explicit prerequisite workflow: get the map from napkin_deck_outline first, navigate by 1-based slide number. It names the alternative source of information and states the condition selecting this tool.

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