batch_decorate

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutation ('apply') and notes Pro gating, but does not state whether existing decorations are overwritten, how partial failures are handled, what permissions are needed, or what the operation returns.

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 core purpose is front-loaded in a clear first sentence, but the remaining two lines are largely marketing copy about Pro features and an upgrade URL. This tier information is relevant to access but crowds out behavioral and parameter guidance.

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?

This is a batch mutation tool with eight parameters, no annotations, and no output schema. The description covers the basic purpose and Pro requirement but omits behavioral details, parameter semantics, output expectations, and error handling that an agent would need to call it correctly.

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?

The description adds no meaning for any of the eight parameters beyond the schema. With only 63% schema description coverage and required fields like content and model_paths lacking descriptions, the description should compensate but does not mention face, mode, scale, depth_mm, material, or output_dir.

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 first sentence clearly states the specific verb and resource: apply the same decoration to multiple models. It distinguishes the batch behavior from single-model decoration siblings implicitly through 'multiple models.' However, it does not name any sibling alternative or clarify scope further.

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 states a prerequisite ('Requires Kiln Pro') but gives no guidance on when to use this tool versus apply_decoration, decorate_surface, or smart_decorate. There are no exclusions, alternatives, or context for selecting batch vs. single-model decoration.

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