generate_necklace_model_wearing

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

With no annotations provided, the description carries the full burden and does describe output style, framing, and the 'authentic luxury brand campaign' aesthetic. It does not disclose return format, output details, or any generation caveats, but for a straightforward image generation tool this is a reasonable middle-ground disclosure.

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 compact at around three sentences and front-loads the core purpose. The framing detail and style note each add value, though 'neck close-up' and the jawline-to-chest framing are slightly redundant.

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?

The description adequately conveys the intended visual result and the schema fully documents parameters. However, with no output schema or annotations, a brief note on what the tool returns or how it processes multiple reference images would make it more complete.

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 both reference_image_urls and aspect_ratio are already documented in the input schema. The description adds no additional parameter-level meaning, which is acceptable under the high-coverage baseline.

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 generates a realistic close-up photo of a necklace worn on a model, with specific framing from jawline/chin to upper chest. The 'worn on model' and 'luxury brand campaign photography' phrasing effectively distinguishes it from sibling tools like generate_necklace_tabletop_elegant and generate_necklace_white_background.

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 clearly conveys that this tool is for necklace-on-model campaign-style imaging, giving strong contextual signals about when to use it. However, it does not explicitly name alternatives or state when not to use it, such as for tabletop or white-background shots.

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