Lists all slides in the current document with their IDs, titles, and shape counts. Use it to survey deck structure before editing or reordering slides.
List all slides in the document (id, title, shape count).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral context. It discloses the returned fields (id, title, shape count), which is useful, but does not state that the operation is read-only, what permissions are needed, or whether it covers the current document only.
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?
A single front-loaded sentence with no wasted wording. The parenthetical return fields are compact and useful.
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 zero-parameter, read-only listing tool with no annotations or output schema, the description is nearly complete: it states the scope and the key fields returned. A minor gap is that it does not explicitly say it applies to the current document.
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 tool has zero parameters, so the baseline is 4. There is no parameter semantics to clarify, and the description does not introduce confusing parameter-like details.
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 ('List') and resource ('all slides in the document'), making the operation clear. It does not explicitly distinguish itself from siblings like document.get_slide or document.list_shapes, so it stops short of a 5.
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?
Usage is implied: call this when you need an inventory of slides. The description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance versus document.get_slide or document.list_shapes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.