prepare_slideshow_assets

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

With no annotations, the description carries full burden. It discloses key behaviors: no Gemini call, downloads images, returns ordered MCP image blocks with image_index labels, and optionally returns audio. It omits error handling or URL validation details, but adequately describes core behavior for a fetch-and-return tool.

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 short paragraphs with no wasted sentences. The first sentence front-loads the primary purpose. Every sentence adds value: sourcing, behavior, usage guidance, and optional audio mention.

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?

With an output schema present, the description need not detail return format beyond 'ordered MCP image blocks with image_index label.' It covers all critical aspects: purpose, sources, client-side usage, and audio option. Minor gaps like size limits or error behavior do not significantly impair completeness.

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?

Both parameters have 100% schema description coverage. The tool description repeats the source types from the schema for 'url' and adds context about returning ordered images, but adds minimal new meaning beyond the schema. The audio parameter's behavior is already well-described in the schema.

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 clearly states the tool returns slideshow images as ordered MCP image blocks, specifying exact sources (TikTok Photo Mode, Instagram photo/carousel, YouTube community post). It distinguishes itself from sibling video analysis tools by focusing on client-side image inspection and explicitly noting it does not call Gemini.

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 explicit usage context: 'Use it when you want Claude/the client AI to inspect the images itself instead of receiving a Gemini-generated analysis.' It does not list when not to use or mention alternatives, but the guidance is clear and actionable given the sibling tools are video-focused.

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