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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false): it discloses that hidden slides are omitted, that slide numbers and the workspace mark are not drawn, that a single slide returns a PNG while multiple return a named .zip, and where the file is saved. This is exactly the extra context annotations cannot carry.

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 core action and resolutions, then covers return shape, exclusions, and the post-call user instruction. It is dense but every sentence carries distinct information; the resolution list is slightly verbose but justified as concrete examples.

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 no-output-schema export tool, the description supplies the return shape (PNG vs .zip naming), the delivery channel (workspace files plus downloadUrl), and the exact agent behavior expected (give the user the link and note it is in their files). Nothing needed 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 description coverage is 100%, so the schema already documents boardId, workspace, and slides including 1-based indexing and the omit-for-all default. The description reinforces the multi-vs-single-slide behavior but adds little syntactic detail beyond the schema, so it sits above the baseline 3 but not at the top.

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 (exports) and resource (a deck's slides as PNG images), and immediately grounds it in concrete output formats and resolutions. The final sentence explicitly redirects PDF/PowerPoint needs to the deck's File menu, distinguishing this tool from that alternative.

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?

Explicitly says when to use it (exporting deck slides as PNGs ready for ad platforms or social posts) and when not to (PDF or PowerPoint — use the File menu instead). It also clarifies the agent-follow-up action of handing the user the downloadUrl.

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