Generate a full catalogue from a ready-made photoshoot set

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the job is billed per shot, that completion requires polling, and that resultUrls will hold all outputs once finished. It is transparent about the core runtime contract, though it does not cover failure modes or permission/credit implications.

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 two tight sentences with the main action and scope front-loaded. Billing, async polling, and result-location facts are each delivered in compact clauses without redundancy or filler.

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?

For a 5-parameter tool with no output schema and no annotations, the description covers the operation, set selection, polling, and result location. Optional parameters like ratio and modelId are left mostly to the schema, but the essential invocation path is complete enough for an agent to act.

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 80%, so most parameters are already documented and the description does not need to compensate. It reinforces shotIds as a subset mechanism and images as product photo(s), but it adds no real detail for undocumented fields like ratio. This is adequate but does not go beyond 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 names a specific operation (running product photos through a ready-made photoshoot set), a bounded resource (Fashio's curated sets), and a concrete outcome (one image per shot). By referencing list_ready_template_sets and get_generation, it clearly separates this tool from single-generation siblings like create_generation.

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 implicitly walks the agent through a flow: pick a set via list_ready_template_sets, submit the job, then poll get_generation. However, it never explicitly states when to prefer this tool over create_generation or any other alternative, and it offers no 'do not use when...' conditions beyond the inherent per-shot cost.

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