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

Goes well beyond annotations: sequential one-image-at-a-time processing, per-photo failure isolation, JPEG export for looks, time-budget truncation returning `remaining`, and credit charging. Annotations only supply the generic safety/idempotency flags; the description supplies the operational reality.

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?

A dense but front-loaded paragraph that puts purpose first and then handles sources, args, edge cases, and cost. Every sentence carries information, though the single-block format makes some details (failure handling, remaining) slightly harder to scan than bullet-style would.

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?

No output schema exists, yet the description explains what comes back (collected download links, `remaining`) and how errors surface. For a non-idempotent, open-world mutation tool, everything an agent needs to invoke and re-invoke it correctly is present.

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 the baseline is 3, but the description adds genuine meaning: that `sources` accepts 'upload:<id>' handles or https URLs and that one link can carry several photos, and that `args` is the preset's arguments minus `image`, with a concrete example ({marketplace: "etsy_square"}).

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?

Opens with a specific verb+resource+scope: 'Run ONE preset over several photos in one call,' then enumerates the exact preset names it can batch. An agent can distinguish this from the single-photo sibling presets (apply_look, product_shot, etc.) purely from the description.

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?

States when to use it (several photos, same arguments), the constraint that opens the door ('Only presets you can call yourself can be batched'), and the continuation path when the time budget is exhausted ('call again with those'). Also implies the single-call alternative by tying costs back to 'the single calls'.

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