batch_set_property

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

With no annotations, the description carries the burden. It discloses that the operation is a single undoable action and confined to the edited scene, which is useful. However, it doesn't describe overwrite behavior, potential failure modes, or what happens if some nodes lack the property.

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?

One sentence, front-loaded with the action verb, no redundant information. Every word contributes to understanding the tool's function.

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?

The description covers the core behavior and scope, but with no output schema it doesn't explain return values, errors, or edge cases. It's adequate for a straightforward batch set but leaves some operational details unanswered.

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 description coverage is 0%, so the description must compensate. It identifies type as the engine class, property as the property to set, and value as the value to set. This is helpful but doesn't elaborate on accepted formats or constraints beyond the schema's basic types.

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?

Description clearly states the action ('Set one property on every node of a given engine class in the edited scene') with a specific verb and resource. It distinguishes from siblings like update_property (single node) and cross_scene_set_property (cross-scene).

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?

Provides clear context: applies to a class of nodes, targets the edited scene, and is undoable. Though it doesn't explicitly mention alternatives, the scope and purpose imply appropriate use versus single-node or cross-scene operations.

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