Import live store screenshots

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

Annotations declare a non-read-only, non-destructive, non-idempotent write, and the description adds real context beyond them: new slides are created plain and already carry their text, and the call returns a count of placed images. It stops short of saying whether existing slides are overwritten or what happens when the store page has no screenshots.

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 the action first, the slide-placement effect second, and the return value last; the parenthetical about plain slides is genuinely informative rather than filler.

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 two-parameter write tool with no output schema, the description covers the action, the side effect on slides, and the return value. The remaining gap is what happens to pre-existing slides and failure behavior, which an agent would want before invoking a non-idempotent write.

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 coverage is 100%, so both parameters are already documented, including the 'default: main' locale behavior. The description restates the locale default but adds no format or edge-case meaning beyond the schema, so the baseline 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 ('Download the screenshots on the app's live store page') plus the concrete effect ('put them on slides in order'), which clearly separates it from siblings like screenshots_export, screenshots_upload, and screenshots_add_image.

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 only implied: the agent can infer this is the way to pull existing live-store imagery into a project, but the description never says when to prefer it over screenshots_export or screenshots_add_image, nor any prerequisites such as a linked app.

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