batch_set_node_properties

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

Despite the annotation already indicating idempotentHint, the description adds significant behavioral details: it avoids startup cost, uses same value-conversion rules as set_node_property, explains abortOnError behavior, confirms save-once semantics, and specifies the return format. This provides a comprehensive understanding of the tool'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 description is extremely concise with three sentences that efficiently cover purpose, usage guidance, behavioral details, and return format. It is front-loaded with the most critical information and contains no unnecessary words.

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 the tool's complexity (batch operation, multiple parameters, sibling tools), the description is remarkably complete. It covers purpose, usage, behavior, parameter nuances, and return format. Without an output schema, it explicitly describes the result structure, ensuring the agent understands the tool's output.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining that value conversion rules match set_node_property (clarifying the 'value' parameter) and elaborates on abortOnError. This goes beyond the schema descriptions, earning a higher score.

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 the tool's purpose: setting multiple node properties in a single Godot process. It explicitly distinguishes itself from the sibling tool set_node_property by noting that it avoids the ~3s startup per call, making it the preferred method for batch updates.

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 provides explicit guidance on when to use this tool over set_node_property, citing performance benefits. It also explains the abortOnError behavior and that it saves once at the end. However, it does not explicitly state when to use set_node_property for single property updates, though this is implied.

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