bulk_set_actor_property

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

With no annotations provided, the description carries full burden. It discloses that it composes set_actor_property, mirrors bulk_*_assets shape, each assignment has own triple, and continue_on_error defaults true. Explains per-assignment failure behavior. Lacks details on atomicity or response structure, but adequately transparent.

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?

Four sentences, well-structured: starts with purpose, then relates to siblings, clarifies what it is NOT, and gives usage context. No unnecessary 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?

Given no output schema and no annotations, the description covers purpose, usage, parameter constraints, and error behavior. Could mention success/failure response format, but overall sufficiently complete for a bulk tool with two parameters.

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 baseline is 3. Description adds significant value: clarifies max 200 entries, each actor/property non-empty, and explains continue_on_error behavior. Adds constraints and context beyond 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 uses a specific verb-resource combination ('apply many UPROPERTY mutations') and clearly distinguishes itself from set_actor_property and the bulk_*_assets family by explaining the composite nature and per-assignment structure.

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 clear usage context: 'useful after batch-spawning to push initial-state mutations without N round-trips.' Explicitly clarifies it is NOT 'set the same property on N actors' but individual sets. Could mention when to use alternatives, but provides good guidance.

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