create_iphone_mockups_batch

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

No annotations are provided, so the description carries the full burden. It discloses that jobs without explicit out path are written to output_dir as NN_<screenshot-name>.png, and lists all parameters and defaults. It does not mention error handling, potential file overwrites, or permissions, but for a file-creating tool, the behavior is reasonably transparent.

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 well-structured: a one-sentence purpose, followed by workflow guidance, then an Args list. It is concise with no unnecessary words, making it easy for an agent to parse quickly.

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 that an output schema exists (not shown), the description does not need to explain return values. It covers the main purpose, workflow, parameter defaults, and output behavior. The only minor gap is the undocumented add_frame parameter, but overall it is 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 description coverage is 0%, so the description must add meaning. It explains most parameters in the Args section, but the 'add_frame' parameter from the schema is missing from the description. The description adds value over the schema but is not exhaustive.

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 'Create App Store preview mockups for many screenshots in one call.' It specifies the verb (Create), the resource (App Store preview mockups), and distinguishes itself from siblings by emphasizing batch processing, differentiating from create_iphone_mockup and suggest_themes.

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?

Explicit guidance is provided: 'If the user did not dictate the titles, draft one per screenshot... show the user the full list, and get approval or edits before calling this.' This tells the agent when to use and when to seek approval, and implies that for a single mockup, the sibling tool should be used.

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