batch_generate_products

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Pro-tier gate, but says nothing about what happens on batch failure, whether photos are consumed, rate limits, or the shape of the result. The injected MAKE DOORS paragraph describes other tools, not this one's behavior.

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 first sentence is tight and front-loaded. The MAKE DOORS block, feature list, and pricing URL are boilerplate that does not describe this tool and dilutes the definition, though the core is still compact.

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 9-parameter, no-annotation, no-output-schema tool, the description covers the tier gate but leaves batch semantics, failure behavior, and output shape unexplained. It is adequate to start an invocation but not 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 coverage is 78%, so the schema documents most of the 9 parameters already. The description adds only the loose mapping 'N photos' to the photos array and 'N products' to the batch count, with no clarification of mode, material, size_mm, or text_template.

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 opening sentence gives a specific verb and resource with scope: 'Generate N decorated products from N photos in one call (Pro).' That distinguishes it from the singular generate_decorated_product and from batch_decorate. However, it never names those siblings, so the differentiation is inferential rather than explicit.

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?

It states the batch/photo use case and that Kiln Pro is required, which implies when to use it. But the only named alternatives (design_session, compile_scad) belong to a different task entirely (the make loop), so there is no real when-to-use-this-vs-a-sibling guidance.

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