lunaar_product_shot_variants

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

Discloses credit consumption and fallback behavior for open_interior. With no annotations, description carries full burden but omits operational details like parallelism, rate limits, or response format.

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?

Single paragraph that front-loads purpose and credit cost, then enumerates variant types. Efficient but could benefit from bullet points for clarity.

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?

Covers main function, variant details, credit cost, fallback, and dimension requirements. Lacks output description but no output schema exists. Sufficient for agent use.

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?

Adds significant meaning to variantTypes by explaining each type and to dimension parameters for scale_reference. Schema coverage is only 50%, so description compensates with context for half the parameters.

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?

Clearly states it generates variants of a previously rendered product shot, listing specific variant types and explaining their behaviors. Distinguishes from sibling tool lunaar_product_shot by requiring a parent.

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?

Provides context that it requires a parent shot and explains when to use scale_reference with dimensions. Does not explicitly exclude alternatives or state when not to use, but the sibling context and description make usage clear.

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