batch-set-layer-properties

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

With no annotations, the description carries full burden. It discloses that setting position clears existing keyframes first, a critical behavioral trait. However, it does not mention behaviors for other properties (e.g., whether scale or rotation also clear keyframes).

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?

Two sentences, front-loaded with purpose and list, followed by a crucial behavioral note. No wasted words; every sentence earns its place.

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 batch operation with no output schema and no annotations, the description covers the basic functionality but omits details like return values, partial failure handling, or error conditions (e.g., layer not found). Adequate but not fully comprehensive.

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 parameters are already well-described. The description adds value by noting the keyframe-clearing behavior for position, which goes beyond the schema. The list of settable properties also reinforces parameter meanings.

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 it sets transform/visibility properties on MANY layers in one call, listing the specific properties (threeDLayer, position, etc.) and targeting methods (layerIndex or layerName). This distinguishes it from sibling tools that operate on single layers or single properties.

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 batch usage by emphasizing 'MANY layers' and listing what can be set, but does not explicitly state when not to use or mention alternatives. It provides clear context for when to use it over single-layer tools.

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