lunaar_jewelry_tryon

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

No annotations provided, and the description only mentions credit costs per mode. It fails to disclose other behavioral traits such as authentication, rate limits, or error handling, leaving the agent with insufficient behavioral context.

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 concise with one sentence stating purpose and credit costs. It is front-loaded with the main verb and resource, but could benefit from slightly more structure to improve readability.

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 (6 parameters, 4 enums) and no output schema, the description lacks complete context. It does not describe return values, success criteria, or common use cases, making it insufficient for reliable tool invocation.

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 50%, with some parameters documented in the schema (e.g., gender, aspectRatio). The description adds credit cost context but does not explain the meaning or usage of parameters beyond what's in the schema.

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 composites jewelry onto a model or surface, with specific credit costs per display mode. This distinguishes it from sibling tools like lunaar_glasses_tryon by focusing on jewelry.

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 implies usage for jewelry try-on with different modes and credit costs, but does not explicitly state when to use or avoid this tool versus alternatives like lunaar_studio_tryon.

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