slides_getImages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects like directory creation, overwrite behavior, file naming conventions, or authentication requirements. This is a significant gap for a file-downloading operation.

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 a single sentence that is front-loaded with the action and resource. It contains no filler or redundant information, earning full marks for conciseness.

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?

The tool is relatively simple with only two parameters, but the description lacks details about return values, error conditions, or whether the local directory must already exist. Given the absence of annotations and output schema, more contextual information would improve completeness, but the basic purpose is adequately covered.

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% (both localPath and presentationId have descriptions), so the schema already documents the parameters. The description does not add extra meaning beyond what the schema provides, earning the baseline of 3.

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 'Downloads all images from a presentation to a local directory' clearly identifies the specific verb (download), resource (images from a presentation), and destination (local directory). It distinguishes itself from sibling tools like slides_getSlideThumbnail, which handles individual thumbnails, and slides_getText, which handles text extraction.

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?

The description provides no guidance on when to use this tool versus alternatives such as slides_getSlideThumbnail or slides_getText. It does not mention when to choose this over other slides tools, nor does it specify exclusions or prerequisites.

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