capture_batch

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

With no annotations provided, the description carries the burden well: it discloses execution behavior (parallel), return content (inline JPEGs + per-sketch metadata), and a real side effect (writes full-res PNGs to snapshots/ in local mode). It still omits whether the operation touches sketch state and any cost/limit behavior for large batches.

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?

Three short sentences, zero waste, and the core action is front-loaded before the return-format and mode-specific details. Each sentence contributes distinct information.

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 5-parameter tool with no output schema and no annotations, the description covers the essentials: what it returns, that it returns images inline, and the local-mode filesystem write. A note on batch-size limits or interaction with other capture tools would close the remaining gap.

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 seed, width, height, sketchIds and previewSize are already documented in the schema. The description adds no extra meaning about overrides or the "default: all sketches" behavior, so the baseline of 3 applies.

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 and resource ("Capture screenshots of multiple sketches") plus the parallel execution mode. The plural "multiple sketches" implicitly separates it from the sibling capture_screenshot, but no sibling is named explicitly.

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?

Batch-vs-single usage is only implied by "multiple sketches"; there is no explicit instruction on when to choose capture_batch over capture_screenshot, preview_sketch, design_capture_composite, or export_sketch. No exclusions, prerequisites, or batch-size guidance are given.

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