maestro_store_screenshot

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

No annotations provided, so the description carries full burden. It explains the core behavior (compositing with Gemini, resizing to store dimensions) and the two input modes. However, it does not disclose potential side effects like file overwriting, rate limits, or authorization requirements. The description is adequate but not exhaustive.

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 concise sentences that front-load the purpose and then detail capabilities. Every word earns its place; no extraneous 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?

Given the complexity (8 parameters, no output schema, no annotations), the description covers the main workflow and options. It lacks explicit description of return values (e.g., file paths created), but the outputDir parameter implies saved files. Overall, it is mostly complete for an agent to use effectively.

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 baseline is 3. The description adds value by explaining that screenshotPath is optional and auto-captures if omitted, and that devices defaults to 'required sizes only.' This enriches understanding beyond the schema descriptions.

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's purpose: 'Create professional app store marketing screenshots with headline text and device-framed app screenshot.' It specifies the action (create), resource (marketing screenshots), and method (using Gemini AI, resizing). This distinguishes it from siblings like maestro_screenshot (simple capture) and generate_screenshot (generic generation).

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 mentions two usage modes: auto-capture from simulator or accept an existing screenshot path. This gives context for when to use each mode, but it does not explicitly state when to use this tool over alternatives (e.g., when needing store-specific formatting vs. a plain screenshot).

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