batch_operations

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

Annotations cover read-only/destructive/idempotent flags, and the description adds valuable context about process behavior and performance: it runs in a single Godot process versus separate processes per operation. This goes beyond the annotations, though it does not cover failure semantics or side effects, hence a 4 rather than 5.

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 two sentences, front-loaded with the core purpose, and every sentence earns its place by providing either functional intent or usage context. No filler or repetition.

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 moderate complexity of a batch operation and the rich schema with nested operation definitions, the description plus schema is sufficient for an agent to understand invocation. It lacks details about error handling or atomicity, but the performance guideline and clear purpose make it nearly complete.

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% for both projectPath and operations, so the structured fields already provide full parameter documentation. The description itself adds no parameter-specific guidance, so the baseline of 3 is appropriate.

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 executes multiple scene operations in a single Godot process invocation, distinguishing it from individual scene-operation tools. The verb 'execute' plus the resource 'scene operations' makes the purpose unambiguous.

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 an explicit usage guideline: 'Use for 3+ operations,' and justifies it by noting performance gains over separate process spawns. This gives the agent clear criteria for when to choose this tool over individual operations.

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